Failures in low-code agents for community users in Europe

Final update

## Customer impact On October 1, 2026, from 10:50 to 19:50 UTC, some Studio Web users in Europe couldn't debug agents that call Orchestrator processes (RPA, agents, etc.) or Action Apps from the same solution. The call failed with a "not found" error. Published agents and production jobs were not affected. ## Root cause A Studio Web update changed how solution resources are located during debugging. It was missing a setting that keeps the previous behavior, so debug runs looked for the solution's resources in the user's personal workspace instead of the debug folder. ## Detection Automated end-to-end tests alerted our engineers at 16:43 UTC. The end-to-end testing suite runs once every 2 hours and alerting only happens after 3 consecutive test failures. The issue was also reported from a customer environment. ## Response After identifying the root cause, a rollback was started at 18:00 UTC and was fully in effect at 19:50 UTC. This duration included a deployment failure that had to be retried, which took 50 minutes. A corrected version that includes the setting was deployed on October 2 at 13:00 UTC. ## Follow up 1. The setting is now part of the main code line, so future releases

1. Postmortem · Oct 7, 14:28 UTC
   ## Customer impact On October 1, 2026, from 10:50 to 19:50 UTC, some Studio Web users in Europe couldn't debug agents that call Orchestrator processes (RPA, agents, etc.) or Action Apps from the same solution. The call failed with a "not found" error. Published agents and production jobs were not affected. ## Root cause A Studio Web update changed how solution resources are located during debugging. It was missing a setting that keeps the previous behavior, so debug runs looked for the solution's resources in the user's personal workspace instead of the debug folder. ## Detection Automated end-to-end tests alerted our engineers at 16:43 UTC. The end-to-end testing suite runs once every 2 hours and alerting only happens after 3 consecutive test failures. The issue was also reported from a customer environment. ## Response After identifying the root cause, a rollback was started at 18:00 UTC and was fully in effect at 19:50 UTC. This duration included a deployment failure that had to be retried, which took 50 minutes. A corrected version that includes the setting was deployed on October 2 at 13:00 UTC. ## Follow up 1. The setting is now part of the main code line, so future releases include it. 2. We're improving the alerts and the end-to-end testing suite to catch regressions earlier.
2. Resolved · Oct 1, 20:08 UTC
   We have confirmed that the rollback has completed and the issue affecting low-code agents that use solution-local action apps for community users in Europe has been resolved. Services have recovered, and we are closing this incident.
3. Identified · Oct 1, 18:25 UTC
   We have identified the issue causing failures in low-code agents that use solution-local action apps for community users in Europe. We are rolling back the previous changes and continuing to monitor the recovery. We will provide another update once rollback is complete or if we have additional information to share.
4. Investigating · Oct 1, 18:17 UTC
   Starting October 1 at approximately 12:00 PM UTC, community users in Europe may experience failures in LowCode Agents that use solution-local Action Apps. We have confirmed the impact is limited to community users in Europe. We are actively investigating the issue, determining the extent of the failures, and working on a fix.