Multiple Regions - Agents and RPA - Web Search GenAI Activity Outage

Update timeline

1. investigating Mar 10, 2026, 06:01 PM UTC

   We are investigating reports of an outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions. Impact: Users may be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our teams are working to understand the cause and scope and will share updates as available.

2. identified Mar 10, 2026, 07:49 PM UTC

   We have identified the cause of the outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions and are working on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our focus is on restoring service as quickly as possible.

3. monitoring Mar 11, 2026, 07:31 AM UTC

   The fix has been deployed and services have been restored. We will continue to monitor system stability before marking the incident as resolved.

4. resolved Mar 11, 2026, 08:10 AM UTC

   The issue has been resolved. Our monitoring indicates that services are operating normally, and no further impact has been observed.

5. postmortem Mar 31, 2026, 02:28 PM UTC

   **Customer Impact** Between 2026-03-10 13:54 UTC and 2026-03-11 08:00 UTC, the web Search tool experienced a service disruption. During this window, automated Agents and RPA workflows requiring real-time web search functionality encountered execution failures. **Root Cause** The disruption was caused by an upstream API quota exhaustion triggered by an atypical spike in request volume. The specific legacy endpoint used for this service maintains a fixed, inelastic daily throughput limit. Due to the provider’s deprecation schedule, standard scalability options are currently restricted. This forced a shift from automated infrastructure adjustments to manual traffic management to maintain service stability during the transition period. **Resolution** To restore service and prevent a recurrence, our engineering team deployed a multi-tenant rate-limiting policy. This ensures that high-volume requests from a single source cannot impact global service availability. Service was fully restored once the upstream provider’s daily telemetry window was reset. **Follow-Up Actions** * **Service Migration:** Since the current provider is deprecating this API, we are accelerating the transition to a more scalable, high-throughput web search alternative to ensure elastic capacity. * **Granular Governance:** Permanent implementation of per-organization request caps to ensure fair resource distribution and prevent individual workflow spikes from impacting the broader user base.