Incident with using workflow_dispatch for Actions
This summary is created by Generative AI and may differ from the actual content.
Overview
On November 1, 2025, between 2:30 UTC and 6:14 UTC, Actions workflows could not be triggered manually from the UI, impacting all customers queueing workflows from the UI for most of the impact window. The Workflow Dispatch API remained unaffected. The incident was caused by a faulty code change in the UI, which was subsequently reverted. Detection was delayed due to an alerting gap for UI-specific issues when underlying APIs were healthy.
Impact
Actions workflows could not be triggered manually from the UI for 3 hours and 44 minutes (2:30 UTC to 6:14 UTC). This impacted all customers attempting to queue workflows from the UI for most of the duration.
Trigger
A faulty code change introduced in the UI.
Detection
Detection was delayed due to an alerting gap for UI breaks in this specific area, as all underlying APIs continued to report as healthy. This suggests awareness came from external reports or manual observation.
Resolution
The faulty code change in the UI was promptly reverted once the impact was identified, mitigating the issue.
Root Cause
The root cause was a faulty code change in the UI. Delayed detection was attributed to an alerting gap for UI breaks in this area, as all underlying APIs were functioning correctly.