help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Subscription Endpoint gets disabled

‎04-14-2016 06:07

‎04-14-2016 06:07

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? 

 

Best Answer
Labels:
0 Votes
1 REPLY 1

‎04-14-2016 08:45

‎04-14-2016 08:45

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 

Best Answer
0 Votes