Status: Failed Error: Access Token expired for resource owner id

Hi @-1092275730, @Jennifer Cole, I'm glad to inform you that we have fix this issue ahead of the planned schedule. If your flows are active, you'll need to de-active and re-activate them to take effect.  Here are some info for those at may be looking at this post. These impact event base trigger on certain systems that have token expiration date/time on a routine basis. Composer will refresh this token if it detects that it has expire. But composer will log an error that will be shown the the run history page and send the email error notification (if enabled). Since the Composer retry is successful, the flow will run and execute successfully (it will have a log a different error otherwise).

Below is an example of a event base trigger on Jira (New issue). The token expires every hour and it logs (alert) the error on the hour. Composer did successfully connect to Jira to check for new events many times between those hours (It didn't show on the run history page because there wasn't any new record created in Jira to be picked up). After de-activating and re-activating the flow. These retry-able errors are filtered out.

** Time of screen shot is 10/9/22 9:45pm PST.

  Please do let me know if you questions or more info.

Thanks

Sai