Tasks remain in the queued state on some worker queues.

Final update

The incident has been resolved.

1. Resolved · Sep 8, 20:09 UTC
   The incident has been resolved.
2. Monitoring · Sep 8, 19:42 UTC
   A fix has been implemented, and we are monitoring the results.
3. Identified · Sep 8, 12:33 UTC
   We have identified the cause. On Astro, each worker queue is backed by a Kubernetes autoscaling resource whose name is built from a fixed platform prefix, the deployment release name, and the worker queue name. For a very small number of customers, where that combined name exceeds the Kubernetes 63-character limit, the autoscaling resource is rejected at creation. As a result, workers do not scale for the affected queue and tasks routed there remain in the queued state. This is why the limit can be reached even when the worker queue name itself looks short: the release name and platform prefix already consume a large portion of the 63 characters before the queue name is appended. Workaround: If affected, until the permanent fix is deployed, please keep worker queue name at or below 10 characters. We are preparing a permanent fix. Further updates to follow.