Multiple Regions - Orchestrator - issues executing processes using target execution bindings

Update timeline

1. identified Mar 09, 2026, 01:21 PM UTC

   We have identified the cause and are working on mitigation. Impact: Some users may experience issues when executing processes using target execution bindings. Additional updates will be provided as we move toward resolution. Affected Regions: - Europe - US - Japan - Australia - Canada - Singapore - India - UK - Switzerland - Delayed US - Delayed EU

2. identified Mar 09, 2026, 01:27 PM UTC

   We have identified the cause and are working on mitigation. Impact: Some users may experience issues when executing any process using target execution bindings. Additional updates will be provided as we move toward resolution. Affected Regions: - Europe - US - Japan - Australia - Canada - Singapore - India - UK - Switzerland - Delayed US - Delayed EU

3. identified Mar 09, 2026, 02:26 PM UTC

   Our team is actively working toward a resolution. We will provide the next update as soon as more information becomes available.

4. identified Mar 09, 2026, 07:34 PM UTC

   A fix has been developed and deployed to our lower environments for validation. We are currently testing the changes to ensure stability before proceeding with a wider rollout. We plan to deploy the fix across production environments once validation is complete. Additional updates will be provided as we make progress toward full resolution.

5. monitoring Mar 10, 2026, 10:45 AM UTC

   The fix has been successfully applied in the following regions and is functioning as expected: European Union, United States, India, Australia, Canada, UK, Switzerland, Delayed-US, and UAE. We are in the process of rolling out the changes to the remaining regions and validating them

6. resolved Mar 10, 2026, 01:15 PM UTC

   The issue has been resolved. A fix was deployed to the remaining regions and the system has remained stable during the monitoring period.

7. postmortem Mar 16, 2026, 09:36 AM UTC

   ## _Customer Impact_ Region\(s\) affected: Global—All regions Service\(s\) affected: Orchestrator Customers using automation workflows with multiple manually configured Package Requirements execution settings, could experience job failures with the following error: > “_Machine doesn’t exist” \(Error code: 1002\)_ The underlying issue was a pre-existing bug that surfaced under a specific sequence of process edits. It was reported on March 6, 2026 and fully resolved on March 10, 2026. ## _Root Cause_ When updating a process with execution settings configured without modifying the execution settings, some settings with empty default values could be incorrectly overwritten. ## _Detection_ The problem was found on March 6, 2026, when a customer service ticket was opened. A customer reported that their automation workflow was failing with a "Machine doesn't exist" error upon execution. The issue had gone undetected until this point, as the bug manifests under a specific sequence of edits and produces no warnings at the time the corrupted data is saved. ## _Response_ Upon receiving the report, engineering triaged the issue and identified the root cause. A workaround was provided to affected customers while a proper fix was developed. The hotfix was rolled out across all regions between March 9–10, 2026, and a database cleanup was applied to remediate all affected processes, fully restoring job execution. ## _Follow-Up_ The bug has been fixed and a database cleanup has been done to fix all affected processes. To prevent recurrence, we are taking the following preventative measures: * Add checks to reject incorrect machine reference values before they are saved. * Incorporating this scenario into our test suite to detect similar issues in future releases.