Orphaned deleted workflow path BuildFailed (id 386397444) blocks every Actions run

[TheWatchProject]

Repository: The-Watch-LLC/The-Watch-Multiproject (private)

Every Actions event completes as startup_failure with 0 jobs and no logs. Push and pull_request events are attributed to a deleted workflow that is not in git:

• workflow id: 386397444
• node id: W_kwDOT7SUMs4XB_UE
• path: BuildFailed
• name: empty
• state: deleted
• created_at / updated_at: 2026-10-16T01:50:34-05:00 (identical)
• absent from GET /actions/workflows
• no BuildFailed file in git history

workflow_dispatch of a real workflow is attributed to that workflow and still creates 0 jobs. Example: Infrastructure CI run 41396672937 (workflow_id 362087423, path .github/workflows/infrastructure.yml), after the file was confirmed to call only actions/checkout at a full SHA.

Repo Actions permissions: enabled=true, allowed_actions=selected, sha_pinning_required=true, github_owned_allowed=true, verified_allowed=true, patterns_allowed=[].

Repo-side calls already tried:

• PUT /actions/workflows/386397444/enable → 403 Unable to enable a workflow that is not active.
• DELETE /actions/workflows/386397444 → 404
• Disable Actions on the repository, wait 3 minutes, re-enable with the same selected-actions policy → ghost row still state=deleted, next dispatch still startup_failure / 0 jobs (run 41396672937)

Last run that actually created jobs was 2026-10-01. Named startup_failure runs continued until 2026-10-16T06:50:34Z, which is the ghost's created_at. Every event since then hits this registration.

Please purge or re-index workflow id 386397444 for this repository so real workflows can start. This matches the orphaned BuildFailed registry bug in community discussions 190193, 204465, 206023, and 206902.

[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.

[jarek-dylewski]

Try gh workflow disable 386397444 and then delete its runs through the REST API, which has cleared ghost workflows for others. In Buddy each pipeline is its own object defined in YAML, so removing one via the UI, bdy CLI or REST API actually removes it.