Resolved -
A fix has now been deployed and the issue is fully resolved.
During the affected period, some executions appeared to remain in a Processing state even though execution had already completed. Executions were not blocked or lost, and executions completed successfully.
However, for impacted executions:
- Analytics metrics may be inaccurate.
- If an execution was triggered by a plan, the associated plan may appear stuck.
Any executions showing as Processing from 3rd February, 3:00pm GMT (as visible in project activity) may need to be manually cancelled before being retried, if required. Once the affected executions are cancelled, any associated plans will automatically become unblocked and resume normal operation.
We apologise for any inconvenience or confusion this may have caused and thank you for your patience.
Feb 4, 15:53 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 4, 12:48 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 4, 12:47 UTC
Investigating -
We are currently investigating this issue.
Feb 4, 11:38 UTC