Orphaned deleted Actions workflow (path "BuildFailed", id 344058418) blocks every workflow start

[blutterback]

Bug: orphaned deleted Actions workflow (path=BuildFailed) blocks every workflow start

Same class of GitHub-side orphan as https://github.com/orgs/community/discussions/204465. There is no remaining repository-side remediation.

Repository

ClearStrideHQ/ClearStride-Marketplace (org admin on a Free plan)

Orphan workflow

• workflow_id: 344058418
• node_id: W_kwDOQMgJks4Ugeoy
• GET /repos/ClearStrideHQ/ClearStride-Marketplace/actions/workflows/344058418 returns 200
• path: BuildFailed
• name: ""
• state: deleted
• created_at / updated_at: 2026-08-27T19:23:57Z (identical)
• html_url: https://github.com/ClearStrideHQ/ClearStride-Marketplace/blob/main/BuildFailed
• Absent from GET /repos/ClearStrideHQ/ClearStride-Marketplace/actions/workflows
• No BuildFailed file exists on main or staging; none in git history

Repo-side APIs already exhausted

• PUT .../actions/workflows/344058418/disable → 403 Unable to disable a workflow that is not active.
• PUT .../actions/workflows/344058418/enable → 403 Unable to enable a workflow that is not active.
• DELETE .../actions/workflows/344058418 → 404
• GraphQL node(id: "W_kwDOQMgJks4Ugeoy") still resolves __typename: Workflow

Impact

Every Actions event since 2026-08-27T19:23:57Z is startup_failure with zero jobs. Sample of 100 newest post-orphan runs: 100/100 startup_failure. GitHub Status is operational (indicator: none).

This includes:

• push / pull_request / pull_request_target / workflow_run (ghost runs: name="", path=BuildFailed, workflow_id=344058418)
• Real workflow_dispatch of an unchanged, previously-green workflow (run is attributed to the real workflow id, still 1-second startup_failure, jobs.total_count=0)

Reproductions

What	Run	Event	SHA	Result
Last healthy Deploy Shared Staging	33102543629	push	fd3f0d5c53220e8310410797a3cb983a2e7e4c91	success at 2026-08-27T18:15:14Z (before the orphan)
Ghost intercept of later push	33132503187	push	716e28fcba8bba84abf37b586d1b95feb69fa8cd	startup_failure, path=BuildFailed, workflow_id=344058418
Real Deploy Shared Staging dispatch	33132522999	workflow_dispatch	same tip	startup_failure in 1s, workflow_id=335671352, jobs=0
Earlier real dispatch at prior tip	33112965751	workflow_dispatch	727cd9cbc747d648d898251a0b757e5b7d14bc4c	same 1s startup_failure
Unrelated workflow	Report Staging Change Surface 33113… dispatches after 19:23Z	workflow_dispatch	n/a	startup_failure

Deploy Shared Staging YAML at the first failing tip (727cd9cbc) is byte-identical to the last green Hosting publish (fd3f0d5c). Repo Actions remain enabled; org allowed_actions=all.

What we will not do

We will not recreate a root file named BuildFailed, rename real workflows, or toggle Actions off/on unless staff asks. Those steps can mask the symptom without removing the orphan registry row.

Request

Please remove or repair the stale Actions workflow registry entry for workflow id 344058418 on ClearStrideHQ/ClearStride-Marketplace so ordinary workflows can start jobs again.

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.