アーカイブ済み公式INCIDENT

Actions delays in starting runs

GitHub・最後の保存提供元状態:resolved

現在のサービス報告 →

公式情報源の文章は原語で表示します。

過去の証拠です。

最後の保存インシデント状態は現在サービス状態ではありません。一覧は不完全の場合があり、情報源からの消失は復旧確認ではありません。最新証拠は現在報告・公式情報源を開いてください。

保存インシデント詳細

提供元状態
resolved
提供元が報告する影響
minor
提供元記録の作成
24 Aug 2026, 13:56:54 UTC
提供元記録の更新
25 Aug 2026, 01:36:32 UTC
提供元が明記した開始
24 Aug 2026, 13:56:54 UTC
提供元が明記した終了
24 Aug 2026, 14:34:42 UTC

提供元が報告した影響を受けるコンポーネント

  • Actions br0l2tvcx85d

関連はインシデント報告範囲で、現在コンポーネント可用性や検証依存関係を証明しません。

記録の作成時刻が障害開始時刻とは限りません。未報告の時刻は不明のままです。収集時刻から停止時間を算出しません。

保存リビジョンの提供元更新

新しい順です。最新の保存内容20リビジョンから最大100件の異なる更新を表示します。同じ提供元時刻の文章変更も別に保持します。

  1. resolved

    On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. <br /> <br />The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely degraded and unable to perform disk operations, it continued sending healthy signals, preventing the system from immediately moving its work elsewhere. During this period, events assigned to the affected component accumulated until an automatic rebalance redirected processing to healthy components at 13:54 UTC. The queue backlog was cleared at 14:00 UTC, and processing returned to normal by 14:04 UTC. <br /><br />To prevent a recurrence, we are improving detection and automated remediation for unhealthy nodes that aren’t fully offline. We are also strengthening application-level resiliency, so stalled consumers are automatically removed quickly and their work reassigned without waiting for the affected node to recover.

    保存リビジョンでの確認:06 Oct 2026, 13:58:39 UTC
  2. monitoring

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

    保存リビジョンでの確認:06 Oct 2026, 13:58:39 UTC
  3. investigating

    Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.

    保存リビジョンでの確認:06 Oct 2026, 13:58:39 UTC
  4. investigating

    We are investigating reports of degraded performance for Actions

    保存リビジョンでの確認:06 Oct 2026, 13:58:39 UTC