UiPath Status

Postmortem: Customer impact

On October 15, 2026, from 11:15 to 12:50 UTC (about 1 hour and 35 minutes), some events exchanged between UiPath cloud services were not delivered. Customers in all commercial cloud regions were affected. During this window:

• New agent runs could stay in Pending status. Running agents waiting on a tool result, a human escalation, document extraction, or context grounding might not resume.
• Conversational agents and Autopilot for Everyone conversations that started an automation might not have received its result.
• Maestro process instances waiting on a user task might not have moved forward after the task was completed, and processes triggered by Integration Service connector events might not have started.
• Apps showing or reacting to queue item status could show outdated information.
• Solution installs, uninstalls, publishes, and deployments could fail or time out.
• Some user, group, and folder changes made in the window might not have propagated to all services.

Work started after 12:50 UTC was not affected. Robot job execution, queues, and triggers handled inside Orchestrator kept working normally.

Root cause

We were moving the delivery of internal service configuration to a new mechanism, a change intended to have no effect on customers. When this change was applied to the event delivery service, the configuration it produced was missing a required value. Without it, the service treated several product integrations as turned off and silently stopped delivering their events. Because the change reached all production regions at the same time, every region was affected.

Detection

The issue was detected at 11:51 UTC, about 35 minutes after impact began, when monitoring alerted on agent jobs remaining in Pending status. Reports of solution deployments timing out followed, and an incident was declared at 12:12 UTC.

Response

Following the first detection at 11:51 UTC, the configuration change was identified and a rollback was started at 12:00 UTC. An initial rollback at 12:14 UTC did not fully restore delivery. The team then stopped the new configuration delivery process and restored the previous configuration. Event delivery began recovering at 12:40 UTC, and full recovery across all regions was confirmed at 12:50 UTC. Where possible, we replayed missed events so that affected work could continue.

Follow up

1. The new configuration delivery process has been paused for the affected service and will stay paused until the configuration is generated correctly.
2. Validate configuration produced by the new delivery mechanism for required values before it is applied to any environment.
3. Roll out changes to configuration delivery progressively across regions instead of to all regions at once.
4. Improve our monitoring to detect within minutes when events stop being delivered to a product integration that normally receives them.
5. Improve our ability to recover and redeliver events missed during a disruption.

Resolved: This incident has been resolved. Between 11:15 and 12:45 UTC on October 15, an internal configuration issue prevented some events from being delivered between UiPath services across multiple regions. The issue was resolved by rolling back the change, and new activity is being processed normally. Some work initiated or in progress during this window may require attention:

• Agents: Agents waiting on Action Center tasks or automation tool results may remain stuck. Jobs started from Orchestrator may also appear stuck or time out.
• Maestro: Processes waiting on user tasks may not have resumed after task completion.
• Apps: Queue item statuses may be outdated, and actions triggered by queue item completion may not have run.
• Autopilot for Everyone: Conversations waiting for automation results may remain stalled.
• Document Understanding and Context Grounding: Automations and agents waiting for extraction, validation, or indexing may remain suspended.
• Integration Service: Connector events may not have triggered the expected processes or notifications.
• Solutions and Studio Web: Solution installs, uninstalls, publishes, deployments, and validations initiated during this window may have failed or timed out. Retrying these operations may resolve the issue.

We apologize for the disruption and thank you for your patience.

Monitoring: The issue has been mitigated. We are monitoring the affected services across regions to ensure stability and confirm that job starts and solution deployments are functioning normally.

Investigating: Since approximately 11:17 UTC, customers across multiple regions have experienced issues with UiPath Agents and Solutions Management. New jobs may remain in Pending status, and running agents may experience delays when processing escalations or waiting for tool results. We are investigating the issue and working toward a resolution.

Postmortem: Customer impact

On October 15, 2026, from 11:15 to 12:50 UTC (about 1 hour and 35 minutes), some events exchanged between UiPath cloud services were not delivered. Customers in all commercial cloud regions were affected. During this window:

• New agent runs could stay in Pending status. Running agents waiting on a tool result, a human escalation, document extraction, or context grounding might not resume.
• Conversational agents and Autopilot for Everyone conversations that started an automation might not have received its result.
• Maestro process instances waiting on a user task might not have moved forward after the task was completed, and processes triggered by Integration Service connector events might not have started.
• Apps showing or reacting to queue item status could show outdated information.
• Solution installs, uninstalls, publishes, and deployments could fail or time out.
• Some user, group, and folder changes made in the window might not have propagated to all services.

Work started after 12:50 UTC was not affected. Robot job execution, queues, and triggers handled inside Orchestrator kept working normally.

Root cause

We were moving the delivery of internal service configuration to a new mechanism, a change intended to have no effect on customers. When this change was applied to the event delivery service, the configuration it produced was missing a required value. Without it, the service treated several product integrations as turned off and silently stopped delivering their events. Because the change reached all production regions at the same time, every region was affected.

Detection

The issue was detected at 11:51 UTC, about 35 minutes after impact began, when monitoring alerted on agent jobs remaining in Pending status. Reports of solution deployments timing out followed, and an incident was declared at 12:12 UTC.

Response

Following the first detection at 11:51 UTC, the configuration change was identified and a rollback was started at 12:00 UTC. An initial rollback at 12:14 UTC did not fully restore delivery. The team then stopped the new configuration delivery process and restored the previous configuration. Event delivery began recovering at 12:40 UTC, and full recovery across all regions was confirmed at 12:50 UTC. Where possible, we replayed missed events so that affected work could continue.

Follow up

1. The new configuration delivery process has been paused for the affected service and will stay paused until the configuration is generated correctly.
2. Validate configuration produced by the new delivery mechanism for required values before it is applied to any environment.
3. Roll out changes to configuration delivery progressively across regions instead of to all regions at once.
4. Improve our monitoring to detect within minutes when events stop being delivered to a product integration that normally receives them.
5. Improve our ability to recover and redeliver events missed during a disruption.

Resolved: This incident has been resolved. Between 11:15 and 12:45 UTC on October 15, an internal configuration issue prevented some events from being delivered between UiPath services across multiple regions. The issue was resolved by rolling back the change, and new activity is being processed normally. Some work initiated or in progress during this window may require attention:

• Agents: Agents waiting on Action Center tasks or automation tool results may remain stuck. Jobs started from Orchestrator may also appear stuck or time out.
• Maestro: Processes waiting on user tasks may not have resumed after task completion.
• Apps: Queue item statuses may be outdated, and actions triggered by queue item completion may not have run.
• Autopilot for Everyone: Conversations waiting for automation results may remain stalled.
• Document Understanding and Context Grounding: Automations and agents waiting for extraction, validation, or indexing may remain suspended.
• Integration Service: Connector events may not have triggered the expected processes or notifications.
• Solutions and Studio Web: Solution installs, uninstalls, publishes, deployments, and validations initiated during this window may have failed or timed out. Retrying these operations may resolve the issue.

We apologize for the disruption and thank you for your patience.

Monitoring: The issue has been mitigated. We are monitoring the affected services across regions to ensure stability and confirm that job starts and solution deployments are functioning normally.

Investigating: Since approximately 11:17 UTC, customers across multiple regions have experienced issues with UiPath Agents and Solutions Management. New jobs may remain in Pending status, and running agents may experience delays when processing escalations or waiting for tool results. We are investigating the issue and working toward a resolution.

Resolved: Some customers in the US region experienced delays in robot log ingestion, with increased activity observed between approximately 11:20 and 11:45 UTC. The issue has been resolved, and log ingestion has returned to normal. Thank you for your patience.

Postmortem: Customer impact

On October 15, 2026, from 11:15 to 12:50 UTC (about 1 hour and 35 minutes), some events exchanged between UiPath cloud services were not delivered. Customers in all commercial cloud regions were affected. During this window:

• New agent runs could stay in Pending status. Running agents waiting on a tool result, a human escalation, document extraction, or context grounding might not resume.
• Conversational agents and Autopilot for Everyone conversations that started an automation might not have received its result.
• Maestro process instances waiting on a user task might not have moved forward after the task was completed, and processes triggered by Integration Service connector events might not have started.
• Apps showing or reacting to queue item status could show outdated information.
• Solution installs, uninstalls, publishes, and deployments could fail or time out.
• Some user, group, and folder changes made in the window might not have propagated to all services.

Work started after 12:50 UTC was not affected. Robot job execution, queues, and triggers handled inside Orchestrator kept working normally.

Root cause

We were moving the delivery of internal service configuration to a new mechanism, a change intended to have no effect on customers. When this change was applied to the event delivery service, the configuration it produced was missing a required value. Without it, the service treated several product integrations as turned off and silently stopped delivering their events. Because the change reached all production regions at the same time, every region was affected.

Detection

The issue was detected at 11:51 UTC, about 35 minutes after impact began, when monitoring alerted on agent jobs remaining in Pending status. Reports of solution deployments timing out followed, and an incident was declared at 12:12 UTC.

Response

Following the first detection at 11:51 UTC, the configuration change was identified and a rollback was started at 12:00 UTC. An initial rollback at 12:14 UTC did not fully restore delivery. The team then stopped the new configuration delivery process and restored the previous configuration. Event delivery began recovering at 12:40 UTC, and full recovery across all regions was confirmed at 12:50 UTC. Where possible, we replayed missed events so that affected work could continue.

Follow up

1. The new configuration delivery process has been paused for the affected service and will stay paused until the configuration is generated correctly.
2. Validate configuration produced by the new delivery mechanism for required values before it is applied to any environment.
3. Roll out changes to configuration delivery progressively across regions instead of to all regions at once.
4. Improve our monitoring to detect within minutes when events stop being delivered to a product integration that normally receives them.
5. Improve our ability to recover and redeliver events missed during a disruption.

Resolved: This incident has been resolved. Between 11:15 and 12:45 UTC on October 15, an internal configuration issue prevented some events from being delivered between UiPath services across multiple regions. The issue was resolved by rolling back the change, and new activity is being processed normally. Some work initiated or in progress during this window may require attention:

• Agents: Agents waiting on Action Center tasks or automation tool results may remain stuck. Jobs started from Orchestrator may also appear stuck or time out.
• Maestro: Processes waiting on user tasks may not have resumed after task completion.
• Apps: Queue item statuses may be outdated, and actions triggered by queue item completion may not have run.
• Autopilot for Everyone: Conversations waiting for automation results may remain stalled.
• Document Understanding and Context Grounding: Automations and agents waiting for extraction, validation, or indexing may remain suspended.
• Integration Service: Connector events may not have triggered the expected processes or notifications.
• Solutions and Studio Web: Solution installs, uninstalls, publishes, deployments, and validations initiated during this window may have failed or timed out. Retrying these operations may resolve the issue.

We apologize for the disruption and thank you for your patience.

Monitoring: The issue has been mitigated. We are monitoring the affected services across regions to ensure stability and confirm that job starts and solution deployments are functioning normally.

Investigating: Since approximately 11:17 UTC, customers across multiple regions have experienced issues with UiPath Agents and Solutions Management. New jobs may remain in Pending status, and running agents may experience delays when processing escalations or waiting for tool results. We are investigating the issue and working toward a resolution.

Postmortem: Customer impact

On October 15, 2026, from 11:15 to 12:50 UTC (about 1 hour and 35 minutes), some events exchanged between UiPath cloud services were not delivered. Customers in all commercial cloud regions were affected. During this window:

• New agent runs could stay in Pending status. Running agents waiting on a tool result, a human escalation, document extraction, or context grounding might not resume.
• Conversational agents and Autopilot for Everyone conversations that started an automation might not have received its result.
• Maestro process instances waiting on a user task might not have moved forward after the task was completed, and processes triggered by Integration Service connector events might not have started.
• Apps showing or reacting to queue item status could show outdated information.
• Solution installs, uninstalls, publishes, and deployments could fail or time out.
• Some user, group, and folder changes made in the window might not have propagated to all services.

Work started after 12:50 UTC was not affected. Robot job execution, queues, and triggers handled inside Orchestrator kept working normally.

Root cause

We were moving the delivery of internal service configuration to a new mechanism, a change intended to have no effect on customers. When this change was applied to the event delivery service, the configuration it produced was missing a required value. Without it, the service treated several product integrations as turned off and silently stopped delivering their events. Because the change reached all production regions at the same time, every region was affected.

Detection

The issue was detected at 11:51 UTC, about 35 minutes after impact began, when monitoring alerted on agent jobs remaining in Pending status. Reports of solution deployments timing out followed, and an incident was declared at 12:12 UTC.

Response

Following the first detection at 11:51 UTC, the configuration change was identified and a rollback was started at 12:00 UTC. An initial rollback at 12:14 UTC did not fully restore delivery. The team then stopped the new configuration delivery process and restored the previous configuration. Event delivery began recovering at 12:40 UTC, and full recovery across all regions was confirmed at 12:50 UTC. Where possible, we replayed missed events so that affected work could continue.

Follow up

1. The new configuration delivery process has been paused for the affected service and will stay paused until the configuration is generated correctly.
2. Validate configuration produced by the new delivery mechanism for required values before it is applied to any environment.
3. Roll out changes to configuration delivery progressively across regions instead of to all regions at once.
4. Improve our monitoring to detect within minutes when events stop being delivered to a product integration that normally receives them.
5. Improve our ability to recover and redeliver events missed during a disruption.

Resolved: This incident has been resolved. Between 11:15 and 12:45 UTC on October 15, an internal configuration issue prevented some events from being delivered between UiPath services across multiple regions. The issue was resolved by rolling back the change, and new activity is being processed normally. Some work initiated or in progress during this window may require attention:

• Agents: Agents waiting on Action Center tasks or automation tool results may remain stuck. Jobs started from Orchestrator may also appear stuck or time out.
• Maestro: Processes waiting on user tasks may not have resumed after task completion.
• Apps: Queue item statuses may be outdated, and actions triggered by queue item completion may not have run.
• Autopilot for Everyone: Conversations waiting for automation results may remain stalled.
• Document Understanding and Context Grounding: Automations and agents waiting for extraction, validation, or indexing may remain suspended.
• Integration Service: Connector events may not have triggered the expected processes or notifications.
• Solutions and Studio Web: Solution installs, uninstalls, publishes, deployments, and validations initiated during this window may have failed or timed out. Retrying these operations may resolve the issue.

We apologize for the disruption and thank you for your patience.

Monitoring: The issue has been mitigated. We are monitoring the affected services across regions to ensure stability and confirm that job starts and solution deployments are functioning normally.

Investigating: Since approximately 11:17 UTC, customers across multiple regions have experienced issues with UiPath Agents and Solutions Management. New jobs may remain in Pending status, and running agents may experience delays when processing escalations or waiting for tool results. We are investigating the issue and working toward a resolution.

Postmortem: Customer impact

On October 15, 2026, from 11:15 to 12:50 UTC (about 1 hour and 35 minutes), some events exchanged between UiPath cloud services were not delivered. Customers in all commercial cloud regions were affected. During this window:

• New agent runs could stay in Pending status. Running agents waiting on a tool result, a human escalation, document extraction, or context grounding might not resume.
• Conversational agents and Autopilot for Everyone conversations that started an automation might not have received its result.
• Maestro process instances waiting on a user task might not have moved forward after the task was completed, and processes triggered by Integration Service connector events might not have started.
• Apps showing or reacting to queue item status could show outdated information.
• Solution installs, uninstalls, publishes, and deployments could fail or time out.
• Some user, group, and folder changes made in the window might not have propagated to all services.

Work started after 12:50 UTC was not affected. Robot job execution, queues, and triggers handled inside Orchestrator kept working normally.

Root cause

We were moving the delivery of internal service configuration to a new mechanism, a change intended to have no effect on customers. When this change was applied to the event delivery service, the configuration it produced was missing a required value. Without it, the service treated several product integrations as turned off and silently stopped delivering their events. Because the change reached all production regions at the same time, every region was affected.

Detection

The issue was detected at 11:51 UTC, about 35 minutes after impact began, when monitoring alerted on agent jobs remaining in Pending status. Reports of solution deployments timing out followed, and an incident was declared at 12:12 UTC.

Response

Following the first detection at 11:51 UTC, the configuration change was identified and a rollback was started at 12:00 UTC. An initial rollback at 12:14 UTC did not fully restore delivery. The team then stopped the new configuration delivery process and restored the previous configuration. Event delivery began recovering at 12:40 UTC, and full recovery across all regions was confirmed at 12:50 UTC. Where possible, we replayed missed events so that affected work could continue.

Follow up

1. The new configuration delivery process has been paused for the affected service and will stay paused until the configuration is generated correctly.
2. Validate configuration produced by the new delivery mechanism for required values before it is applied to any environment.
3. Roll out changes to configuration delivery progressively across regions instead of to all regions at once.
4. Improve our monitoring to detect within minutes when events stop being delivered to a product integration that normally receives them.
5. Improve our ability to recover and redeliver events missed during a disruption.

Resolved: This incident has been resolved. Between 11:15 and 12:45 UTC on October 15, an internal configuration issue prevented some events from being delivered between UiPath services across multiple regions. The issue was resolved by rolling back the change, and new activity is being processed normally. Some work initiated or in progress during this window may require attention:

• Agents: Agents waiting on Action Center tasks or automation tool results may remain stuck. Jobs started from Orchestrator may also appear stuck or time out.
• Maestro: Processes waiting on user tasks may not have resumed after task completion.
• Apps: Queue item statuses may be outdated, and actions triggered by queue item completion may not have run.
• Autopilot for Everyone: Conversations waiting for automation results may remain stalled.
• Document Understanding and Context Grounding: Automations and agents waiting for extraction, validation, or indexing may remain suspended.
• Integration Service: Connector events may not have triggered the expected processes or notifications.
• Solutions and Studio Web: Solution installs, uninstalls, publishes, deployments, and validations initiated during this window may have failed or timed out. Retrying these operations may resolve the issue.

We apologize for the disruption and thank you for your patience.

Monitoring: The issue has been mitigated. We are monitoring the affected services across regions to ensure stability and confirm that job starts and solution deployments are functioning normally.

Investigating: Since approximately 11:17 UTC, customers across multiple regions have experienced issues with UiPath Agents and Solutions Management. New jobs may remain in Pending status, and running agents may experience delays when processing escalations or waiting for tool results. We are investigating the issue and working toward a resolution.

Postmortem: Customer impact

On October 15, 2026, from 11:15 to 12:50 UTC (about 1 hour and 35 minutes), some events exchanged between UiPath cloud services were not delivered. Customers in all commercial cloud regions were affected. During this window:

• New agent runs could stay in Pending status. Running agents waiting on a tool result, a human escalation, document extraction, or context grounding might not resume.
• Conversational agents and Autopilot for Everyone conversations that started an automation might not have received its result.
• Maestro process instances waiting on a user task might not have moved forward after the task was completed, and processes triggered by Integration Service connector events might not have started.
• Apps showing or reacting to queue item status could show outdated information.
• Solution installs, uninstalls, publishes, and deployments could fail or time out.
• Some user, group, and folder changes made in the window might not have propagated to all services.

Work started after 12:50 UTC was not affected. Robot job execution, queues, and triggers handled inside Orchestrator kept working normally.

Root cause

We were moving the delivery of internal service configuration to a new mechanism, a change intended to have no effect on customers. When this change was applied to the event delivery service, the configuration it produced was missing a required value. Without it, the service treated several product integrations as turned off and silently stopped delivering their events. Because the change reached all production regions at the same time, every region was affected.

Detection

The issue was detected at 11:51 UTC, about 35 minutes after impact began, when monitoring alerted on agent jobs remaining in Pending status. Reports of solution deployments timing out followed, and an incident was declared at 12:12 UTC.

Response

Following the first detection at 11:51 UTC, the configuration change was identified and a rollback was started at 12:00 UTC. An initial rollback at 12:14 UTC did not fully restore delivery. The team then stopped the new configuration delivery process and restored the previous configuration. Event delivery began recovering at 12:40 UTC, and full recovery across all regions was confirmed at 12:50 UTC. Where possible, we replayed missed events so that affected work could continue.

Follow up

1. The new configuration delivery process has been paused for the affected service and will stay paused until the configuration is generated correctly.
2. Validate configuration produced by the new delivery mechanism for required values before it is applied to any environment.
3. Roll out changes to configuration delivery progressively across regions instead of to all regions at once.
4. Improve our monitoring to detect within minutes when events stop being delivered to a product integration that normally receives them.
5. Improve our ability to recover and redeliver events missed during a disruption.

Resolved: This incident has been resolved. Between 11:15 and 12:45 UTC on October 15, an internal configuration issue prevented some events from being delivered between UiPath services across multiple regions. The issue was resolved by rolling back the change, and new activity is being processed normally. Some work initiated or in progress during this window may require attention:

• Agents: Agents waiting on Action Center tasks or automation tool results may remain stuck. Jobs started from Orchestrator may also appear stuck or time out.
• Maestro: Processes waiting on user tasks may not have resumed after task completion.
• Apps: Queue item statuses may be outdated, and actions triggered by queue item completion may not have run.
• Autopilot for Everyone: Conversations waiting for automation results may remain stalled.
• Document Understanding and Context Grounding: Automations and agents waiting for extraction, validation, or indexing may remain suspended.
• Integration Service: Connector events may not have triggered the expected processes or notifications.
• Solutions and Studio Web: Solution installs, uninstalls, publishes, deployments, and validations initiated during this window may have failed or timed out. Retrying these operations may resolve the issue.

We apologize for the disruption and thank you for your patience.

Monitoring: The issue has been mitigated. We are monitoring the affected services across regions to ensure stability and confirm that job starts and solution deployments are functioning normally.

Investigating: Since approximately 11:17 UTC, customers across multiple regions have experienced issues with UiPath Agents and Solutions Management. New jobs may remain in Pending status, and running agents may experience delays when processing escalations or waiting for tool results. We are investigating the issue and working toward a resolution.

Postmortem: Customer impact

On October 15, 2026, from 11:15 to 12:50 UTC (about 1 hour and 35 minutes), some events exchanged between UiPath cloud services were not delivered. Customers in all commercial cloud regions were affected. During this window:

• New agent runs could stay in Pending status. Running agents waiting on a tool result, a human escalation, document extraction, or context grounding might not resume.
• Conversational agents and Autopilot for Everyone conversations that started an automation might not have received its result.
• Maestro process instances waiting on a user task might not have moved forward after the task was completed, and processes triggered by Integration Service connector events might not have started.
• Apps showing or reacting to queue item status could show outdated information.
• Solution installs, uninstalls, publishes, and deployments could fail or time out.
• Some user, group, and folder changes made in the window might not have propagated to all services.

Work started after 12:50 UTC was not affected. Robot job execution, queues, and triggers handled inside Orchestrator kept working normally.

Root cause

We were moving the delivery of internal service configuration to a new mechanism, a change intended to have no effect on customers. When this change was applied to the event delivery service, the configuration it produced was missing a required value. Without it, the service treated several product integrations as turned off and silently stopped delivering their events. Because the change reached all production regions at the same time, every region was affected.

Detection

The issue was detected at 11:51 UTC, about 35 minutes after impact began, when monitoring alerted on agent jobs remaining in Pending status. Reports of solution deployments timing out followed, and an incident was declared at 12:12 UTC.

Response

Following the first detection at 11:51 UTC, the configuration change was identified and a rollback was started at 12:00 UTC. An initial rollback at 12:14 UTC did not fully restore delivery. The team then stopped the new configuration delivery process and restored the previous configuration. Event delivery began recovering at 12:40 UTC, and full recovery across all regions was confirmed at 12:50 UTC. Where possible, we replayed missed events so that affected work could continue.

Follow up

1. The new configuration delivery process has been paused for the affected service and will stay paused until the configuration is generated correctly.
2. Validate configuration produced by the new delivery mechanism for required values before it is applied to any environment.
3. Roll out changes to configuration delivery progressively across regions instead of to all regions at once.
4. Improve our monitoring to detect within minutes when events stop being delivered to a product integration that normally receives them.
5. Improve our ability to recover and redeliver events missed during a disruption.

Resolved: This incident has been resolved. Between 11:15 and 12:45 UTC on October 15, an internal configuration issue prevented some events from being delivered between UiPath services across multiple regions. The issue was resolved by rolling back the change, and new activity is being processed normally. Some work initiated or in progress during this window may require attention:

• Agents: Agents waiting on Action Center tasks or automation tool results may remain stuck. Jobs started from Orchestrator may also appear stuck or time out.
• Maestro: Processes waiting on user tasks may not have resumed after task completion.
• Apps: Queue item statuses may be outdated, and actions triggered by queue item completion may not have run.
• Autopilot for Everyone: Conversations waiting for automation results may remain stalled.
• Document Understanding and Context Grounding: Automations and agents waiting for extraction, validation, or indexing may remain suspended.
• Integration Service: Connector events may not have triggered the expected processes or notifications.
• Solutions and Studio Web: Solution installs, uninstalls, publishes, deployments, and validations initiated during this window may have failed or timed out. Retrying these operations may resolve the issue.

We apologize for the disruption and thank you for your patience.

Monitoring: The issue has been mitigated. We are monitoring the affected services across regions to ensure stability and confirm that job starts and solution deployments are functioning normally.

Investigating: Since approximately 11:17 UTC, customers across multiple regions have experienced issues with UiPath Agents and Solutions Management. New jobs may remain in Pending status, and running agents may experience delays when processing escalations or waiting for tool results. We are investigating the issue and working toward a resolution.

Postmortem: Customer impact

On October 15, 2026, from 11:15 to 12:50 UTC (about 1 hour and 35 minutes), some events exchanged between UiPath cloud services were not delivered. Customers in all commercial cloud regions were affected. During this window:

• New agent runs could stay in Pending status. Running agents waiting on a tool result, a human escalation, document extraction, or context grounding might not resume.
• Conversational agents and Autopilot for Everyone conversations that started an automation might not have received its result.
• Maestro process instances waiting on a user task might not have moved forward after the task was completed, and processes triggered by Integration Service connector events might not have started.
• Apps showing or reacting to queue item status could show outdated information.
• Solution installs, uninstalls, publishes, and deployments could fail or time out.
• Some user, group, and folder changes made in the window might not have propagated to all services.

Work started after 12:50 UTC was not affected. Robot job execution, queues, and triggers handled inside Orchestrator kept working normally.

Root cause

We were moving the delivery of internal service configuration to a new mechanism, a change intended to have no effect on customers. When this change was applied to the event delivery service, the configuration it produced was missing a required value. Without it, the service treated several product integrations as turned off and silently stopped delivering their events. Because the change reached all production regions at the same time, every region was affected.

Detection

The issue was detected at 11:51 UTC, about 35 minutes after impact began, when monitoring alerted on agent jobs remaining in Pending status. Reports of solution deployments timing out followed, and an incident was declared at 12:12 UTC.

Response

Following the first detection at 11:51 UTC, the configuration change was identified and a rollback was started at 12:00 UTC. An initial rollback at 12:14 UTC did not fully restore delivery. The team then stopped the new configuration delivery process and restored the previous configuration. Event delivery began recovering at 12:40 UTC, and full recovery across all regions was confirmed at 12:50 UTC. Where possible, we replayed missed events so that affected work could continue.

Follow up

1. The new configuration delivery process has been paused for the affected service and will stay paused until the configuration is generated correctly.
2. Validate configuration produced by the new delivery mechanism for required values before it is applied to any environment.
3. Roll out changes to configuration delivery progressively across regions instead of to all regions at once.
4. Improve our monitoring to detect within minutes when events stop being delivered to a product integration that normally receives them.
5. Improve our ability to recover and redeliver events missed during a disruption.

Resolved: This incident has been resolved. Between 11:15 and 12:45 UTC on October 15, an internal configuration issue prevented some events from being delivered between UiPath services across multiple regions. The issue was resolved by rolling back the change, and new activity is being processed normally. Some work initiated or in progress during this window may require attention:

• Agents: Agents waiting on Action Center tasks or automation tool results may remain stuck. Jobs started from Orchestrator may also appear stuck or time out.
• Maestro: Processes waiting on user tasks may not have resumed after task completion.
• Apps: Queue item statuses may be outdated, and actions triggered by queue item completion may not have run.
• Autopilot for Everyone: Conversations waiting for automation results may remain stalled.
• Document Understanding and Context Grounding: Automations and agents waiting for extraction, validation, or indexing may remain suspended.
• Integration Service: Connector events may not have triggered the expected processes or notifications.
• Solutions and Studio Web: Solution installs, uninstalls, publishes, deployments, and validations initiated during this window may have failed or timed out. Retrying these operations may resolve the issue.

We apologize for the disruption and thank you for your patience.

Monitoring: The issue has been mitigated. We are monitoring the affected services across regions to ensure stability and confirm that job starts and solution deployments are functioning normally.

Investigating: Since approximately 11:17 UTC, customers across multiple regions have experienced issues with UiPath Agents and Solutions Management. New jobs may remain in Pending status, and running agents may experience delays when processing escalations or waiting for tool results. We are investigating the issue and working toward a resolution.