-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why retryConfig is only available for scheduled functions? #699
Comments
I found a few problems with this issue:
|
This feature is now even more pressing as Cloud Console changed the UI to edit a function and now we are unable to edit them. See https://issuetracker.google.com/u/0/issues/162440541.
Please advise if there are any workarounds. |
@mbleigh any chance this could be prioritized or maybe you could bump the internal issue related to https://issuetracker.google.com/u/0/issues/162440541. |
I'd like to confirm the problem mentioned by @sk- . There is no way to enable retries for firebase functions using GCP UI now. So it means there is no way to enable retries at all. |
This should be fixed by #760 and available in the next release of firebase-tools. See firebase/firebase-tools#1734 (comment) |
Currently only scheduled functions have a retry config, however all background functions support retries, see https://firebase.google.com/docs/functions/retries.
Given that the underlying technology for all the background functions is pubsub, it should be straightforward to add the retry config to the other function types.
For us this would simplify our development, as a bunch of our firestore triggers are randomly failing either with a RST error, or with no error at all. And having a consistent way of specifying the retries would be quite nice.
The text was updated successfully, but these errors were encountered: