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.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

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.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

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: 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.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

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: 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.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

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.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

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.