Message gets delivered when FCM returns 500 or 503

[George Zografos]

Has anyone come across the following situation? We noticed that Firebase was returning a few 500/503s on March 16th but the notifications were still forwarded and displayed to the users in Android and iOS devices.

Should we or shouldn't we retry sending notifications when FCM returns 500 or 503? I would expect that when this error is returned the push notification would not get sent behind the scenes from FCM.

[Kato Richardson]

Hi George,

Whether you should retry is covered per error code in the FCM reference docs. For 503, you should honor the retry after error. A 500 could be retried with exponential backoff.

☼, Kato

On Wed, Mar 24, 2021 at 3:20 AM George Zografos <george.p...@gmail.com> wrote:

Has anyone come across the following situation? We noticed that Firebase was returning a few 500/503s on March 16th but the notifications were still forwarded and displayed to the users in Android and iOS devices.

Should we or shouldn't we retry sending notifications when FCM returns 500 or 503? I would expect that when this error is returned the push notification would not get sent behind the scenes from FCM.

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/e9d010ac-b907-4c8c-bfa5-0de4208e26cfn%40googlegroups.com.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398