运行启动操作延迟

2026年8月24日，在13:33 UTC至14:04 UTC期间，3.8%的Actions运行遭遇超过5分钟的启动延迟，其中1.25%的Actions运行直接失败。<br /> <br />此次事件由托管多个负责处理runner分配事件的服务实例之一的节点上的磁盘故障引起。通常，不健康节点上的pod会被自动移除并替换，不会产生影响。但在本例中，尽管节点严重降级且无法执行磁盘操作，它仍持续发送健康信号，导致系统未能立即将其工作转移至他处。在此期间，分配给受影响组件的事件不断累积，直到13:54 UTC自动重新平衡将处理工作重定向至健康组件。队列积压于14:00 UTC清除，处理工作于14:04 UTC恢复正常。<br /><br />为防止再次发生，我们正在改进对未完全离线的非健康节点的检测和自动修复机制。同时，我们也在加强应用层面的韧性，以便停滞的消费者能被快速自动移除，其工作无需等待受影响节点恢复即可重新分配。

原文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.

影响Actions的服务降级问题已得到缓解。我们正在监控以确保稳定性。

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

部分客户在排队和运行Actions作业时遇到的故障正在逐步解决。我们正在监控以确认完全恢复。

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

我们正在调查有关Actions性能下降的报告。

原文We are investigating reports of degraded performance for Actions