Robot Job Failures  - EU Region

Final update

## Customer Impact On September 10, 2026, between 10:00 UTC and 17:40 UTC, customers using Automation Cloud in Europe region experienced intermittent failures of unattended robot job executions on the serverless runtime. Affected jobs failed shortly after starting, before any automation work was performed, with errors indicating that a required program file could not be found. Only automations using a specific set of software libraries were affected; the majority of jobs in the region continued to run normally. The job failure rate rose from a normal baseline of approximately 6% to a peak of 30-37%, and approximately 312 job executions failed that would otherwise have succeeded. Affected automations could be re-run successfully once the issue was resolved. No data was lost, and no job produced incorrect results. ## Root Cause To make automations start quickly we keep a pre-built cache of commonly used software packages, so robots do not download them at run time. Two changes combined to cause this incident. A routine update to an internal build tool changed which Application runtime version the cache was built for. Packages ship files for several runtime versions and the cache keep

1. Postmortem · Sep 21, 08:10 UTC
   ## Customer Impact On September 10, 2026, between 10:00 UTC and 17:40 UTC, customers using Automation Cloud in Europe region experienced intermittent failures of unattended robot job executions on the serverless runtime. Affected jobs failed shortly after starting, before any automation work was performed, with errors indicating that a required program file could not be found. Only automations using a specific set of software libraries were affected; the majority of jobs in the region continued to run normally. The job failure rate rose from a normal baseline of approximately 6% to a peak of 30-37%, and approximately 312 job executions failed that would otherwise have succeeded. Affected automations could be re-run successfully once the issue was resolved. No data was lost, and no job produced incorrect results. ## Root Cause To make automations start quickly we keep a pre-built cache of commonly used software packages, so robots do not download them at run time. Two changes combined to cause this incident. A routine update to an internal build tool changed which Application runtime version the cache was built for. Packages ship files for several runtime versions and the cache keeps only those needed, to stay a manageable size; after the update it kept only the newest runtime's files and deleted the ones our robots use. Separately, we store previous dependency calculations so repeat jobs start faster. Those stored results pointed at the deleted files, and the check validating
2. Resolved · Sep 10, 10:00 UTC
   On 10 September 2026 between 10:00 UTC and 17:23 UTC , Subset of customers in the Europe region experienced elevated failure rates for robot jobs due to an issue with the package cache used by the robot executor. The issue has been resolved and the fault rate has returned to baseline levels. Further details will be provided in the RCA.