UiPath Status

Resolved: The issue is fixed and service is healthy.

Monitoring: Team has rolled out the fix and currently monitoring the service health.

Investigating: We are currently experiencing an outage affecting UiPath Data Service across multiple regions. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

To prevent similar incidents in the future, we are taking the following steps:

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.

Resolved: The issue is fixed and service is healthy.

Monitoring: Team has rolled out the fix and currently monitoring the service health.

Investigating: We are currently experiencing an outage affecting UiPath Data Service across multiple regions. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

To prevent similar incidents in the future, we are taking the following steps:

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.

Postmortem: # Customer impact

We understand that this incident disrupted your ability to deploy new agents, and we apologize for the impact on your operations. Between March 25, 2026 at 6:21 am UTC and March 30, 2026 at 6:00 pm UTC—a period of approximately five days—customers in the EU, US, and Asia regions were unable to deploy new agents in certain folders following a transition to the Serverless Machine Runtime.

Existing agents continued to operate normally throughout the incident. If you attempted to deploy a new agent in a folder without a Serverless Machine Runtime provisioned, you encountered errors and were unable to proceed. A workaround was available throughout: you could manually provision a Serverless Machine Runtime at the folder level to immediately unblock new deployments. For organizations where enabling the Serverless Machine Runtime was not viable, our engineering team restored the previous runtime configuration to resume your operations.

Root cause

A recent change transitioned newly deployed agents to run on the Serverless Machine Runtime instead of the previous runtime. This introduced a requirement for a Serverless Machine Runtime to be provisioned at the folder level before new agents could execute.

This requirement was not intended. The system already contained fallback logic for other workloads—such as API Workflows—that would automatically locate or provision a Serverless Machine Runtime when one was not explicitly assigned at the folder level. However, this fallback logic was not applied to agents during the transition, creating a gap in the expected behavior.

As a result, any folder without an explicitly provisioned Serverless Machine Runtime could not run newly deployed agents. Existing agents and folders with templates already assigned remained unaffected because they continued to use their previously configured runtime.

Detection

The issue was first reported by a customer on March 25, 2026 at 6:21 am UTC. Our engineering team was engaged the following day and identified the root cause, approximately one day after the initial report.

We recognize the gap between the issue first surfacing on March 25 and the formal incident declaration approximately five days later on March 30, 2026 at approximately 10:00 am UTC as an area for improvement. While the workaround was communicated during this period, we should have notified you through our status page sooner to ensure you had the information needed to make decisions about your environment.

Response

Following the initial reports on March 25, our engineering team provided workarounds to affected customers. For those of you who were unable to provision Serverless Machine Runtimes, our engineering team restored the previous runtime configuration to resume your operations.

Our engineering team identified the root cause and developed a fix on March 26, 2026, then validated it in a testing environment by March 27, 2026. On March 30, 2026 at approximately 10:00 am UTC, we declared a formal incident to coordinate the deployment of the fix across all affected regions.

The fix ensures that if no Serverless Machine Runtime is found at the folder level, one is automatically selected from the tenant level or provisioned if none exists. We deployed the fix progressively, validated it at each stage, and provided status updates throughout the day. We achieved full recovery by March 30, 2026 at 6:00 pm UTC, when new agent deployments resumed normal operation across all regions without manual intervention.

Follow up

To prevent similar issues in the future, we are expanding our regression testing to validate that new releases properly account for all configuration, deployment, and licensing scenarios—including cases where optional infrastructure components have not been explicitly provisioned at the folder level. We are adding automated test cases that specifically verify fallback behavior across all workload types whenever runtime requirements change, ensuring that agents, API Workflows, and other workloads are validated consistently before any release reaches your environment.

We are also enhancing our monitoring and alerting systems to detect deployment failures of this nature proactively, without relying on customer reports. This includes automated checks that verify new agent deployments succeed across a representative sample of folder configurations immediately after each release, allowing us to identify and resolve issues before they affect you.

Finally, we are reviewing our escalation and communication processes to ensure that when issues are identified, you are notified promptly through our status page. Closing the gap between issue detection and customer communication is a priority so that you have the information you need to take action as quickly as possible. These improvements directly address the gaps this incident exposed—in testing coverage, proactive detection, and customer communication—and will help ensure that future runtime transitions do not disrupt your agent deployments.

Resolved: Issue is now resolved.

Identified: Team is making progress on a fix deployment, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Identified: Team is working on a fix deployment, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Investigating: Uipath Agents that are newly deployed in Canada, Japan and USA will not start unless a serverless machine template is assigned to the folder.

We are working on a fix, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Resolved: The issue is fixed and service is healthy.

Monitoring: Team has rolled out the fix and currently monitoring the service health.

Investigating: We are currently experiencing an outage affecting UiPath Data Service across multiple regions. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

To prevent similar incidents in the future, we are taking the following steps:

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.

Postmortem: # Customer impact

We understand that this incident disrupted your ability to deploy new agents, and we apologize for the impact on your operations. Between March 25, 2026 at 6:21 am UTC and March 30, 2026 at 6:00 pm UTC—a period of approximately five days—customers in the EU, US, and Asia regions were unable to deploy new agents in certain folders following a transition to the Serverless Machine Runtime.

Existing agents continued to operate normally throughout the incident. If you attempted to deploy a new agent in a folder without a Serverless Machine Runtime provisioned, you encountered errors and were unable to proceed. A workaround was available throughout: you could manually provision a Serverless Machine Runtime at the folder level to immediately unblock new deployments. For organizations where enabling the Serverless Machine Runtime was not viable, our engineering team restored the previous runtime configuration to resume your operations.

Root cause

A recent change transitioned newly deployed agents to run on the Serverless Machine Runtime instead of the previous runtime. This introduced a requirement for a Serverless Machine Runtime to be provisioned at the folder level before new agents could execute.

This requirement was not intended. The system already contained fallback logic for other workloads—such as API Workflows—that would automatically locate or provision a Serverless Machine Runtime when one was not explicitly assigned at the folder level. However, this fallback logic was not applied to agents during the transition, creating a gap in the expected behavior.

As a result, any folder without an explicitly provisioned Serverless Machine Runtime could not run newly deployed agents. Existing agents and folders with templates already assigned remained unaffected because they continued to use their previously configured runtime.

Detection

The issue was first reported by a customer on March 25, 2026 at 6:21 am UTC. Our engineering team was engaged the following day and identified the root cause, approximately one day after the initial report.

We recognize the gap between the issue first surfacing on March 25 and the formal incident declaration approximately five days later on March 30, 2026 at approximately 10:00 am UTC as an area for improvement. While the workaround was communicated during this period, we should have notified you through our status page sooner to ensure you had the information needed to make decisions about your environment.

Response

Following the initial reports on March 25, our engineering team provided workarounds to affected customers. For those of you who were unable to provision Serverless Machine Runtimes, our engineering team restored the previous runtime configuration to resume your operations.

Our engineering team identified the root cause and developed a fix on March 26, 2026, then validated it in a testing environment by March 27, 2026. On March 30, 2026 at approximately 10:00 am UTC, we declared a formal incident to coordinate the deployment of the fix across all affected regions.

The fix ensures that if no Serverless Machine Runtime is found at the folder level, one is automatically selected from the tenant level or provisioned if none exists. We deployed the fix progressively, validated it at each stage, and provided status updates throughout the day. We achieved full recovery by March 30, 2026 at 6:00 pm UTC, when new agent deployments resumed normal operation across all regions without manual intervention.

Follow up

To prevent similar issues in the future, we are expanding our regression testing to validate that new releases properly account for all configuration, deployment, and licensing scenarios—including cases where optional infrastructure components have not been explicitly provisioned at the folder level. We are adding automated test cases that specifically verify fallback behavior across all workload types whenever runtime requirements change, ensuring that agents, API Workflows, and other workloads are validated consistently before any release reaches your environment.

We are also enhancing our monitoring and alerting systems to detect deployment failures of this nature proactively, without relying on customer reports. This includes automated checks that verify new agent deployments succeed across a representative sample of folder configurations immediately after each release, allowing us to identify and resolve issues before they affect you.

Finally, we are reviewing our escalation and communication processes to ensure that when issues are identified, you are notified promptly through our status page. Closing the gap between issue detection and customer communication is a priority so that you have the information you need to take action as quickly as possible. These improvements directly address the gaps this incident exposed—in testing coverage, proactive detection, and customer communication—and will help ensure that future runtime transitions do not disrupt your agent deployments.

Resolved: Issue is now resolved.

Identified: Team is making progress on a fix deployment, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Identified: Team is working on a fix deployment, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Investigating: Uipath Agents that are newly deployed in Canada, Japan and USA will not start unless a serverless machine template is assigned to the folder.

We are working on a fix, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Resolved: The issue is fixed and service is healthy.

Monitoring: Team has rolled out the fix and currently monitoring the service health.

Investigating: We are currently experiencing an outage affecting UiPath Data Service across multiple regions. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

To prevent similar incidents in the future, we are taking the following steps:

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.

Resolved: The issue is fixed and service is healthy.

Monitoring: Team has rolled out the fix and currently monitoring the service health.

Investigating: We are currently experiencing an outage affecting UiPath Data Service across multiple regions. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

To prevent similar incidents in the future, we are taking the following steps:

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.