Fitbit "expired_token" but still working?!

Hi

I have a flow that runs each day that move data from my FitBit account to a spreadheet.

Lately I've started getting the following email daily, telling me that the Token has expired.

But when I look at the history, the flow has run just fine, and the data has been read and moved to my spreadheet.

I have tried refreshing the token multiple times, but I still get the daily email with the error.

Hello @infospray,

Thanks for reaching out to us.

Upon checking, we noticed that the Fitbit connection is token-based, and the access token refresh happens automatically at the backend. In some cases, the workflow may attempt execution while the token is in the process of expiring/refreshing, which triggers the expired_token notification email.

However, the token gets refreshed shortly after, and the workflow executes successfully in the subsequent attempt. This is why your task history shows successful executions, and the data is being moved to your spreadsheet as expected.

You do not need to worry—everything is working fine, and no action is required from your side.

Yeah I can see it working, but I would prefer not to get a daily email about it.

When I get the same error each day, I just start to ignore it. And what if some day the token actually expired and I had to re-authorize?

So can you do something so I don't get this warning each day?

As of now, we don’t have the option to stop error notifications from being sent. If you would like this feature to be added to Pabbly Connect, you can submit your request on our dedicated platform.

https://roadmap.pabbly.com/b/Feature-Request

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
? Pabbly.com
?Rate your support