Fitbit Subscribe Disabled

[jinboshen]

hi, Fitbit Team:
   Recently we noticed that our fitbit subscribe has been disabled several times. But there is no error in callback log.

   How many errors are allowed by fitbit callback? Is there anything change in the callback strategy? Because we have the same system runnning for 5 years. only in recently we have this issue keep happening.

   Looking forward for your reply. Thanks. Our client id is: 22CKYN.

Bo Wei

[GordonFitbit · Accepted solution]

Hi @jinboshen 

The subscriberstat log only shows 1000 messages.   Your subscriber receives a lot of notifications, so it's possible the errors are quickly being flushed out of the log available to you.   We document the reason for disabling subscribers in the documentation.   For more information, see https://dev.fitbit.com/build/reference/web-api/developer-guide/using-subscriptions/#Disabled-Subscri....   We have not changed anything with our subscriber/webhook functionality.

I do see a spike of errors that occured from 2025-03-15 23:00 - 2025-03-16 02:00 UTC.  So, you might have seen your subscriber get disabled about that time.   The error messages I'm seeing are read timeouts.  This makes me think that there possibly was an influx of messages that occurred at this time, your subscriber is processing the messages as they come in and you cannot process the messages fast enough.  We recommend that as the notifications arrive, place them into a queue and respond with the 204 immediately.  Then, process the notifications as your system resources permit.

I hope this gives you some insight into the problem.   Let me know if you have further questions.

Gordon

[jinboshen]

Thanks Gordon for your help. We'll look into why those errors occur.