Third confirmed case: deleted BuildFailed workflow causes startup_failure on every push

[antonmurzenko2026-maker]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

This is another confirmed case of the backend issue described in #190193:
https://github.com/orgs/community/discussions/190193

A deleted ghost workflow is created on every push:

• Workflow ID: 339899074
• Path: BuildFailed
• State: deleted
• Conclusion: startup_failure

Affected runs:

• 32560122959
• 32562112620

The real active CI workflow is:

• Workflow ID: 305292297
• Path: .github/workflows/ci.yml
• State: active

No jobs, check runs, runner allocation, or logs are created. The active ci.yml Git blob is identical to the version used by the last successful run, so workflow contents are ruled out.

The Actions budget is available and not exhausted.

Other users report that deleting runs, disabling and re-enabling Actions, reclaiming the BuildFailed path, dummy workflows, and branch or repository renames do not resolve this backend record.

Could GitHub staff please open an internal Actions engineering issue and arrange removal of orphaned workflow registration 339899074?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[antonmurzenko2026-maker]

Clarification: this is an active operational defect, not a feature request. The orphaned BuildFailed registration currently prevents the repository’s valid CI workflow from starting and blocks production release verification.

Could a GitHub Community maintainer please triage this to the GitHub Actions engineering team or provide a private support escalation path?

[ptadigi]

Confirmed affected repository: ptadigi/lavoni-pos (private, repo ID 1256772445).

Orphaned workflow:

• ID 300387563
• path BuildFailed
• state deleted

Active workflows remain valid:

• CI 287456145 (.github/workflows/ci.yml)
• Deploy 287456148 (.github/workflows/deploy.yml)

Fresh events on commit 6276f4ff15106c9c1ee1b2f5ab5f1bd8d590872b were all routed to the deleted workflow and failed before job creation:

• run 33379483201 (push): startup_failure, zero jobs
• run 33379488511 (pull_request): startup_failure, zero jobs
• run 33379525462 (pull_request): startup_failure, zero jobs

Both active workflow files pass actionlint 1.7.12 with zero errors. Repo Actions permissions are enabled. Local Prettier/ESLint/TypeScript/Next production build all pass. Account Actions usage is not exhausted. We also deleted 725 stale artifacts (4.16 GiB) and verified artifacts/cache are now zero; the orphaned BuildFailed routing persists.

A deploy rerun 33369381675 is additionally stuck queued with zero jobs; force-cancel returns HTTP 409 and deletion returns HTTP 403.

This is blocking a production migration where manual deployment is prohibited. Please escalate removal/repair of orphaned workflow registration 300387563 to GitHub Actions engineering.