What you would like to accomplish: In some scenarios when using Real time database triggers or any trigger that uses PubSub internally with Google Cloud Functions as the communication method there might be a benefit to having a shorter ack_deadline to improve instances where a PubSub message requires a re-delivery.
How this might work: An option can be provided when creating the trigger for the Cloud Function where an ack_deadline value can be specified. A suggested minimum and hard maximum should be implemented.
If applicable, reasons why alternative solutions are not sufficient: N/A
Other information (workarounds you have tried, documentation consulted, etc): This feature request will also track the comment made in https://github.com/firebase/firebase-functions/issues/626#issuecomment-1189683520 indicating that if there is a nack or re-delivery required that the ack_deadline will not have to expire and re-delivery will occur immediately.
Description
What you would like to accomplish:
In some scenarios when using Real time database triggers or any trigger that uses PubSub internally with Google Cloud Functions as the communication method there might be a benefit to having a shorter ack_deadline to improve instances where a PubSub message requires a re-delivery.
How this might work:
An option can be provided when creating the trigger for the Cloud Function where an ack_deadline value can be specified. A suggested minimum and hard maximum should be implemented.
If applicable, reasons why alternative solutions are not sufficient:
N/A
Other information (workarounds you have tried, documentation consulted, etc):
This feature request will also track the comment made in