Service disruption for Maestro Flow in South Korea region

Update timeline

1. resolved Sep 18, 2026, 06:03 PM UTC

   During the General Availability (GA) rollout of Maestro Flow, an issue was identified in the South Korea region where one of the scale units had not been deployed, causing the flow to fail.

2. postmortem Oct 22, 2026, 05:31 AM UTC

   ## Customer impact Customers in the South Korea region could not open the Maestro Flow design experience. Creating a Maestro Flow or Maestro Automate project succeeded, but the editor then failed to load with the message "The editor failed to load. Please retry or try again later." The issue affected the design experience only; execution of existing flows was not affected, and no other region was affected. The issue was present from the start of the Maestro Flow public preview on until . It affected 12 trial organisations in the South Korea region; no enterprise customers were affected. ## Root cause Maestro Flow was never deployed to the South Korea infrastructure. When the region was prepared for services in May 2026, Maestro Flow was still in private preview and was intentionally excluded from that region as "not ready yet". That exclusion had no owner or review date. When Maestro Flow later opened to public preview and then to general availability, the product entry points were enabled in South Korea without checking that the service behind them was deployed there. No health check covered Maestro Flow in that region, so the failure was not visible internally until a customer reported it. ## Detection A customer report was received at 08:25 UTC on . No internal alert fired. Investigation confirmed that the Maestro Flow service was absent from the South Korea infrastructure rather than failing after startup. ## Response By 09:49 UTC the Maestro Flow and Maestro Automate entry points were hidden in the South Korea region, so customers no longer encountered the failing editor, and creating a tenant in another region was offered as a workaround. The deployment owners were engaged, and the missing deployment configuration was identified at 17:35 UTC. Maestro Flow was deployed to the South Korea infrastructure at 17:50 UTC and verified working. The configuration was corrected permanently, and the entry points were re-enabled in South Korea at 18:22 UTC. The customer confirmed the fix at 22:00 UTC. The public status page was updated at 18:03 UTC. ## Follow up 1. Automated health checks for Maestro Flow now run in the South Korea, UAE and Switzerland regions, in addition to the regions already covered. Remaining gaps in those checks are being closed. 2. Any decision to exclude a service from a region will require a recorded reason and review date, and stale exclusions will be reported automatically. 3. Enabling a product in a region will require confirming that the service is deployed and monitored in that region first. 4. An alert on editor load failures, per region, is being added as an independent safeguard.