Incident Library
Applied filters Root causeSoftware defectComponentJob scheduler serviceSymptomDuplicate delivery or executionClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    From 1 May 2026, some QStash schedules in the US region behaved wrongly: changes to schedules did not take effect, paused or deleted schedules came back, and newly created schedules did not run as expected. Some scheduled jobs were also executed twice.

    Trigger

    On 1 May 2026 a bug made QStash in the US region send traffic back to the legacy scheduling path, which had been left in the codebase as a fallback after the move to the new scheduling infrastructure.

    Root cause
    Component
    Contributing factor
    Remediation
    • Made the new scheduling system the active source of truth again
    • Reconciled the data between the legacy and new scheduling systems
    • Wrote the missing schedule changes back into the new infrastructure
    • Resolved conflicts to keep user data and schedule continuity
    • Restored some previously paused or deleted schedules to avoid permanent data loss
    Action items
    • Remove obsolete fallback execution paths once a transition is complete
    • Add automated safeguards and alerts for unexpected fallback behaviour
    • Improve consistency validation between the systems
    • Expand rollback and reconciliation testing
Check your cluster for this

This case involves Job scheduler service. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1