Application Subscriber disabled for some reason

[Zarko2022]

Hi,

Can you please check why our subscriber occasionally gets disabled ?
It happened on 23/24 January. And a few more times in January/December.
Application ID is: 227NZ9

Also after it is disabled, it doesn't stop the whole traffic, but it seems it is only stopped for some subscription types ? 

Thank you!

[Zarko2022]

@Gordon-C Can you help us out please ?

[Gordon-C · Accepted solution]

Hi @Zarko2022 

Here is some information on why subscribers get disabled.   See "Disabled subscribers".   I see a couple of things wrong with your subscriber.

1. If you look at the subscriber stats page at https://dev.fitbit.com/apps, you'll see you're responding to the webhooks with a 202.   The correct response is a 204.  See Responding to a Notification.

2. I see some "Read time out" errors in our logs.  This makes me think you are taking too long to read the notification and respond with a 204 (or in your case a 202).   You have 5 seconds to respond to the notification.  If you don't, then an error is generated.   The number of errors generated are likely the cause your subscriber is getting disabled.

If you're trying to process the notifications as they come in, then it is possible these errors are occurring because you cannot process the notifications fast enough.  It would be best to receive the notification, respond with the 204 and then put the notification into a queue to be processed based on your systems' resources.  

[Zarko2022]

Ok, Thank you @Gordon-C. We will try to improve it and see if it keeps happening.