Orchestrator - Customers are experiencing issues in accessing queue item

Final update

## Customer impact Between August 28, 2026 at 3:23 pm UTC and August 28, 2026 at 10:57 pm UTC, a subset of customers experienced errors when opening queue item details panels in Orchestrator. The affected path returned a 404 page for LINKED queues when the user did NOT have access to the original folder in which the items were created. The impact affected only Orchestrator UI interactions and it spanned across all regions running the affected software version. Orchestrator application programming interface access was unaffected, and exporting queue data to CSV was available as a workaround. The total duration was approximately 7 hours. ## Root cause The incident was caused by a regression in the Orchestrator user interface for linked queues accessed from other folders. The regression did not correctly handle the linked-queue details flow when the requesting user lacked access to the original folder, which caused the queue item details panel to route to a 404 page instead of displaying the expected information. ## Detection The issue was detected through an automated incident alert for the Orchestrator front end on August 28, 2026 at 3:23 pm UTC. ## Response At 3:31 pm UTC on August

1. Postmortem · Sep 3, 08:49 UTC
   ## Customer impact Between August 28, 2026 at 3:23 pm UTC and August 28, 2026 at 10:57 pm UTC, a subset of customers experienced errors when opening queue item details panels in Orchestrator. The affected path returned a 404 page for LINKED queues when the user did NOT have access to the original folder in which the items were created. The impact affected only Orchestrator UI interactions and it spanned across all regions running the affected software version. Orchestrator application programming interface access was unaffected, and exporting queue data to CSV was available as a workaround. The total duration was approximately 7 hours. ## Root cause The incident was caused by a regression in the Orchestrator user interface for linked queues accessed from other folders. The regression did not correctly handle the linked-queue details flow when the requesting user lacked access to the original folder, which caused the queue item details panel to route to a 404 page instead of displaying the expected information. ## Detection The issue was detected through an automated incident alert for the Orchestrator front end on August 28, 2026 at 3:23 pm UTC. ## Response At 3:31 pm UTC on August 28, 2026, our engineering team described the issue as customers being unable to access queue item details panels due to a regression. At 3:41 pm UTC, a public status update confirmed that the root cause had been identified, that a fix was being deployed, and that application programming interface a
2. Resolved · Aug 28, 22:57 UTC
   The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.
3. Identified · Aug 28, 20:00 UTC
   The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.
4. Identified · Aug 28, 17:39 UTC
   We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.
5. Monitoring · Aug 28, 17:27 UTC
   We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.
6. Identified · Aug 28, 15:41 UTC
   The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.