GitHub Support: clear four uncancellable July Actions runs

[CompleteDotTech]

GitHub Support: clear four uncancellable July Actions runs

Runs 30158074443, 30158074458, 30158095776, and 30158095786 have remained queued since 2026-07-25. They are obsolete CI/CodeQL history, but both REST cancellation endpoints (/cancel and /force-cancel) consistently return HTTP 500 with adequate API quota, including a fresh retry on 2026-08-10. Do not delete workflow history. Blocked on GitHub Actions backend repair or support intervention; next step: retry the two cancellation endpoints after GitHub resolves the backend state, then close only after all four report completed/cancelled.

Bead metadata

• Bead ID: cave-88pe8

• Status: blocked

• Priority: P2

• Surface: Missing

• Authoritative owner: 68980965+BunsDev@users.noreply.github.com

• Labels: None

• Parent: None

• Dependencies: cave-zsxpd

• Unresolved blockers: cave-zsxpd

Source of truth

Beads is authoritative. This draft card is a GitHub Teamwork visibility mirror and should be reconciled from the Bead rather than edited as an independent task.

[CompleteDotTech]

Retried both cancellation endpoints on 2026-08-24, per the issue's stated next step. No change — still HTTP 500 on both, with ample quota.

All four runs remain status: queued, unchanged since 2026-07-25:

30158074443  queued   POST /cancel -> HTTP 500 "Failed to cancel workflow run"
30158074458  queued   POST /cancel -> HTTP 500
30158095776  queued   POST /cancel -> HTTP 500
30158095786  queued   POST /cancel -> HTTP 500

30158074443  POST /force-cancel -> HTTP 500 "Failed to cancel workflow run"

REST quota at the time of the attempt: core 4889/5000, so this is not throttling. That is now three independent attempts returning 500 — the original, the 2026-08-10 retry recorded in this issue, and this one — over a span of a month.

This remains blocked on GitHub Actions backend repair or support intervention; nothing in this repository can clear it. Workflow history has not been deleted, as the issue directs.

Worth noting for whoever files with support: these four are pure obsolete CI/CodeQL history and are not the cause of the current runner contention, which was measured separately at ~3 concurrent slots against a deep PR queue and is tracked as cave-rqlfe.

[BunsDev]

P0 revalidation and GitHub Support escalation prepared

All four runs remain backend-stuck: queued since 2026-07-25, conclusion: null, zero jobs, empty PR associations, and unchanged timestamps. Both supported mutation paths still fail after today’s resolved Actions incident:

• /cancel: HTTP 500 for all four runs
• /force-cancel: HTTP 500 for all four runs
• delayed post-incident canary at 2026-08-24T14:52:33Z: HTTP 500, request DE00:7E5E4:162A3E4:4AB7829:6A8C5AB1

Fresh request IDs and complete run/workflow/head diagnostics are recorded on Bead cave-zsxpd and in the prepared redacted support packet. GitHub documents that official Actions backend cases can only be submitted through the authenticated Support portal; there is no support-ticket API or gh command. The portal has been opened with the packet copied for submission.

Requested support outcome: move runs 30158074443, 30158074458, 30158095776, and 30158095786 to terminal cancelled state without deleting workflow history.

This issue remains blocked only on GitHub Support intervention and should close after all four REST records report terminal/cancelled.