04-14-2016 06:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-14-2016 06:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello Fitbit team,
We are noticing a high number of failed delivered notifications to our system. The issues seem to have started around 4PM EST, April 13th, 2016. As of midnight of April 14th EST time, our subscription endpoint keeps getting disabled. We are seeing messages making it through but all delivery attempts are marked as failed on Fitbit management console. Also, it seems like the messages being now delivered are very high: messages: over 400 and are over 50K in size. This seems overly high, all of a sudden.
Are there any changes you guys are making or any known issues that might be causing the subscriptions to fail?
04-14-2016 08:45
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-14-2016 08:45
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Noticed the same thing RoxanaF - Given the spike in IDs in the payload, we are likely not handling fast enough before responding with a proper header response.
Luckily, this is an easy enough fix for us. Hopefully that tweak will resolve the timeouts/disabling. But I think you're right RoxanaF. It does appear that they may have reduced the frequency of the notifications and just batched more users per notification.
Thanks -
John

