Resolved -
This incident has been resolved.
Jul 3, 10:33 UTC
Monitoring -
Fix is now live in all regions. Early metrics from monitoring look stable. We'll keep a close eye on everything for the next 30 minutes before declaring full resolution.
Jul 3, 10:05 UTC
Update -
The fix has now been successfully deployed to the UK. As a result, the following regions are now operational: UK, India, UAE, Canada, EU, Australia, Japan, US and Switzerland
Jul 3, 09:54 UTC
Update -
Services have been restored to operational status in India, UAE, Canada, EU, Australia, Japan, US, Switzerland. Validation for the remaining regions (UK, Singapore) is underway.
Jul 3, 08:44 UTC
Update -
Services have been restored to operational status in the EU, Australia, Japan, US and Switzerland. Validation for the remaining regions is underway.
Jul 3, 08:27 UTC
Update -
Deployment and validation for the remaining regions are underway. We will share further updates as soon as they become available.
Jul 3, 07:22 UTC
Update -
The fix is live and working as expected in the US and Japan. We've started deploying it to the remaining affected regions.
Jul 3, 06:11 UTC
Update -
The fix is now live in the US and Japan, and we are monitoring stability in those regions. Concurrently, the team is focused on mitigating the issue across all remaining environments.
Jul 3, 05:09 UTC
Update -
We are continuing to work on a fix for this issue.
Jul 3, 03:47 UTC
Identified -
We have identified the cause of the degraded performance impacting Orchestrator's 'configured execution settings for API trigger job ignored' in US and we are working on mitigation.
Impact: customers might see configured execution settings for API trigger job ignored in orchestrator.
Jul 3, 03:28 UTC
Investigating -
We have identified the issue and currently working on a fix.
Jul 3, 02:24 UTC