Hi there, further to this (still haven’t got it working-using a workaround) I have now had two messages from internals saying wahoo has been disconnected and requesting reconnection. I am also still seeing the red unable to get data from wahoo banner.
Any idea what triggers the disconnect and from which side? Are there any logs for this?
2 Likes
HumanGO is also disconnecting frequently which is a completely separate platform. This is fairly new behavior. It makes me wonder if something is going on with authentication in the Wahoo Cloud API that is impacting multiple users of it.
Probably because Wahoo changed their Authentication flow:
- Applications will be limited to 10 unrevoked access tokens per user starting January 1, 2026. If you receive an error indicating you have exceeded this limit, you are likely refreshing tokens without making API calls with the refreshed tokens. Once an API call is made with the refreshed access token the previous access token will be revoked. Ensure that your app is only refreshing tokens when necessary.
Important: Access tokens should only be refreshed immediately prior to making an API request. Refreshing a token alone does not revoke the previous access token. The previous access token is only invalidated once an API call is successfully made using the newly refreshed access token. Refreshing tokens too early or without subsequently making an API call can result in multiple unrevoked tokens and may cause your application to exceed the per-user token limit.
This is from the Wahoo API documentation:
Authentication – Wahoo Fitness API Reference
I’ve always got first a Red Banner on the top “Error fetching Activities from Wahoo”, and nearly immediately the chat message that I am disconnected.
1 Like
We are looking into this issue. We might have fixed a race condition with token renewal for people uploading planned workouts and downloading planned workouts. Will deploy that on Wed AM.
3 Likes
I have the same problem.
We have fixed another related race condition with Wahoo tokens. Will deploy Sat AM (GMT+2).
The basic issue is that Wahoo revokes the old refresh_token and access_token as soon as a call is made with a newly issued access_token. So any other thread using the old tokens is unable to make calls or renew them.
1 Like
Thanks <3
Any further updates to share? I am also having the same problem.
Seems to be fixed on my end.