UiPath incident
JAPAN - Orchestrator - Robot logs are not showing up for some Customers
Resolved after 25 minutes, affecting Orchestrator, on October 13, 2026.
## Customer impact Between approximately 07:00 UTC on 9 Oct 2026 and 10:45 UTC on 13 Oct 2026, about 6% of robot log entries for customers in the Japan region did not appear in Orchestrator. Job execution and all other Orchestrator functionality were not affected. Missing entries became visible in Orchestrator after the issue was fixed. ## Root cause Robot logs are placed on a queue split into 32 partitions, and an ingestion service reads each partition and stores the logs for Orchestrator. On October 9, the ingestion service in the Japan region stopped reading from 2 of the 32 partitions without reporting an error. Logs on those partitions were kept in the queue but not stored, so they did not appear in Orchestrator. Our monitoring checked the service as a whole, not each partition, so the issue was not detected automatically. ## Detection The issue was detected through customer reports. We declared an incident at 10:13 UTC on October 13 and posted a status page notification at 10:32 UTC. ## Response We restarted the ingestion service at approximately 10:41 UTC, and it resumed reading all partitions. The logs held in the queue were then processed and became visible in Orchestrator. The incident was resolved at 10:57 UTC. ## Follow up * We are adding monitoring that alerts us when any single partition stops being read, so this kind of issue is detected within minutes.
Affected components
Update timeline
- investigating Oct 13, 2026, 10:32 AM UTC
We are investigating issue where robot execution logs are not showing up in Orchestrator. we are working to determine the full scope and root cause.
- resolved Oct 13, 2026, 10:57 AM UTC
This issue has been resolved. Robot execution logs are syncing and are visible in Orchestrator again for Japan Orchestrator. Thank you for your patience.
- postmortem Oct 22, 2026, 01:25 PM UTC
## Customer impact Between approximately 07:00 UTC on 9 Oct 2026 and 10:45 UTC on 13 Oct 2026, about 6% of robot log entries for customers in the Japan region did not appear in Orchestrator. Job execution and all other Orchestrator functionality were not affected. Missing entries became visible in Orchestrator after the issue was fixed. ## Root cause Robot logs are placed on a queue split into 32 partitions, and an ingestion service reads each partition and stores the logs for Orchestrator. On October 9, the ingestion service in the Japan region stopped reading from 2 of the 32 partitions without reporting an error. Logs on those partitions were kept in the queue but not stored, so they did not appear in Orchestrator. Our monitoring checked the service as a whole, not each partition, so the issue was not detected automatically. ## Detection The issue was detected through customer reports. We declared an incident at 10:13 UTC on October 13 and posted a status page notification at 10:32 UTC. ## Response We restarted the ingestion service at approximately 10:41 UTC, and it resumed reading all partitions. The logs held in the queue were then processed and became visible in Orchestrator. The incident was resolved at 10:57 UTC. ## Follow up * We are adding monitoring that alerts us when any single partition stops being read, so this kind of issue is detected within minutes.
Your product runs on more than UiPath
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services