Frequent "Disabled" Status Issue for Client ID 22CCMS

[22BZ3Y]

Dear Fitbit Support Team,

Our Client ID is 22CCMS, with an OAuth 2.0 Application Type of Server.
We have been integrating Fitbit's Activities and Sleep data for several years without major issues.

However, over the past two months, we have been frequently encountering a situation where our application's activities subscription status is switched to Disabled. 

Additionally, we noticed that we are not receiving any notification emails when these status changes occur, which makes it difficult for us to respond proactively.

Could you please assist us in investigating the root cause of these issues?
We would greatly appreciate any guidance or solutions you can provide to help us maintain a stable integration.

Thank you very much for your support and assistance.

[GordonFitbit]

Hi @22BZ3Y 

We recently updated our security libraries and I think it broke the webhook notifications.  I'm working with the engineering team to get this fixed.

[22BZ3Y]

Hi, @GordonFitbit 

Thank you for the update on the webhook notification issue.

We’d also like to understand why our Activities subscription status keeps switching to Disabled repeatedly over the past two months. We haven’t made any changes on our end, so we’re concerned there may be a system-side trigger.

Could you help us identify the root cause and advise how to avoid this in the future?

Thanks again for your support.

[GordonFitbit]

Hi @22BZ3Y 

Would you please re-enable your subscriber and let me know if you start receiving webhook notifications again?