Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in UiPath

Intermittent 503 errors on Test Manager

Resolved Minor
July 30, 2025 - Started 9 months ago - Lasted 5 minutes
Official incident page

Incident Report

Between 2025-06-19 05:00 AM UTC and 2025-06-19 08:30 PM UTC, some API calls in the EU and US regions failed with a 503 error. Customers may have experienced this issue intermittently during that time, but refreshing the page or trying again resolved it. The incident was caused by a bad code push in recent deployment. The issue originated when background jobs were getting initialized. Intermittently, a database call was made after the required service context had already been disposed, resulting in a "connection is closed" error. Eventually, the unhandled exception propagated, causing the pods to crash and restart. Requests that were landed to these restarting pods resulted in a 503 status. Once the issue was identified, it was isolated, fixed, and a hotfix was deployed across all regions. To prevent similar incidents in the future, and to detect such issues earlier, we are implementing the following measures: - Enhancing alerting mechanisms, including alerts for pod health and restarts across all environments - Introducing a more rigorous code review process to catch such issues early in the development cycle

Trusted by 1,000+ teams

Never miss outages in third-party dependencies

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED 9 months ago - at 07/30/2025 07:52AM

Between 2025-06-19 05:00 AM UTC and 2025-06-19 08:30 PM UTC, some API calls in the EU and US regions failed with a 503 error. Customers may have experienced this issue intermittently during that time, but refreshing the page or trying again resolved it.

The incident was caused by a bad code push in recent deployment. The issue originated when background jobs were getting initialized. Intermittently, a database call was made after the required service context had already been disposed, resulting in a "connection is closed" error. Eventually, the unhandled exception propagated, causing the pods to crash and restart. Requests that were landed to these restarting pods resulted in a 503 status.

Once the issue was identified, it was isolated, fixed, and a hotfix was deployed across all regions.

To prevent similar incidents in the future, and to detect such issues earlier, we are implementing the following measures:
- Enhancing alerting mechanisms, including alerts for pod health and restarts across all environments
- Introducing a more rigorous code review process to catch such issues early in the development cycle

INVESTIGATING 9 months ago - at 07/30/2025 07:51AM

Between 2025-06-19 05:00 AM UTC and 2025-06-19 08:30 PM UTC, some API calls in the EU and US regions failed with a 503 error. Customers may have experienced this issue intermittently during that time, but refreshing the page or trying again resolved it.

The incident was caused by a bad code push in recent deployment. The issue originated when background jobs were getting initialized. Intermittently, a database call was made after the required service context had already been disposed, resulting in a "connection is closed" error. Eventually, the unhandled exception propagated, causing the pods to crash and restart. Requests that were landed to these restarting pods resulted in a 503 status.

Once the issue was identified, it was isolated, fixed, and a hotfix was deployed across all regions.

To prevent similar incidents in the future, and to detect such issues earlier, we are implementing the following measures:
- Enhancing alerting mechanisms, including alerts for pod health and restarts across all environments
- Introducing a more rigorous code review process to catch such issues early in the development cycle

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook