Long running syncs
Affected
Partial outage from 11:02 PM to 2:20 AM
- Resolved · UTC
After monitoring the fix implemented we have resolved the issue.
The issue occurred under certain conditions and caused syncs to to not be properly retried.
Thank you for your patience as we investigated this issue and we apologize for any inconvenience.
- Monitoring · UTC
We believe we have found the root cause and have implemented a fix. We will be monitoring the results.
- Investigating · UTC
We are still seeing instances of these long running syncs and failures with
"Setting attempt to FAILED because the temporal workflow for this connection was restarted, and existing job state was cleaned.". We are continuing our investigation and will add updates as we have them. - Update · UTC
We have been monitoring the results over the weekend and would like to continue monitoring throughout the day.
- Monitoring · UTC
We implemented a fix and are currently monitoring the result. Any sync affected will show as a failed sync but the next scheduled sync should run as expected.
- Identified · UTC
We have identified an issue that is causing syncs to run longer than expected. We are taking action to address these long running syncs.
Thank you for your patience as we work to resolve the issue.
