Subscription callback was disabled

[ikbenben]

Hi There,

We have recently had a few complaints from customers that their Fitbit information was not being synced into our application. After invetstigating, the subscription callback url was disabled and I'm wondering if there is a way to find out why this happend. Looking at the details of the callback url, I can see that the last requests to our callback url were on 2015-09-28 and they were returning 204 results

I've reenabled the callback url and we now seem to be receiving data again.

Some follow up questions:

• Is there a way to get the missing data between 2015-09-29 and 2015-10-05?
• We didn't see a notification email when it was disabled. Now this could be because it is going to a non company email address and the person whose email address this belongs to doesn't pay attention to this stuff. It would be great if we could actually change the registered email address. Or if would be great if there are ways to integrate with 3rd party systems such as slack or trello

As far as I understand, we are an affiliate with Fitbit

thanks

Ben 

[SunsetRunner]

Hi Ben,

Unfortunately there is no way to catch up on the missing data. As for the email, I would recommend registering a new Fitbit account with some sort of a shared email/alias for your team and we can transfer ownership of the existing application to this new account.

Can you PM me your application OAuth 2.0 Client ID or OAuth 1.0 consumer key? I can check if your subscriber was disabled for too many failed deliveries.

[aarondcoleman]

@SunsetRunner We were also just disabled.

We've seen an unusually high # of SocketTimeout errors and our endpoint was just disabled. We quickly re-enabled, but are not seeing any unusually high volume on our end and continue to see SocketTimeout issues. Was there a change to the subscriotion API in the last day or so? Any proxy changes or network routing that might be causing this?

[SunsetRunner]

Hey Aaron,

There hasn't been any changes to the system recently and after consulting with another team member, we don't believe there are any network issues. During the time you're API subscriptions subscriber was having issues, there were no increase error rates for anyone else.

[SunsetRunner]

---

@SunsetRunner wrote:

Hi Ben,

Unfortunately there is no way to catch up on the missing data. As for the email, I would recommend registering a new Fitbit account with some sort of a shared email/alias for your team and we can transfer ownership of the existing application to this new account.

Can you PM me your application OAuth 2.0 Client ID or OAuth 1.0 consumer key? I can check if your subscriber was disabled for too many failed deliveries.

---

I followed up with Ben over PM and it does appear his subscriber was auto-disabled due to delivery failures.

[aarondcoleman]

Thanks @SunsetRunner for the quick response. Seems like we contiune to process them, so it must be a hiccup on the response back to your endpoint causing the timeout. Nothing changed here but we just did a quick refresh of all our endpoint nodes and we'll monitor. If you see anything weird from consumers elsewhere, let me know.

--Aaron