Deleted BuildFailed workflow registrations intercept Actions events across multiple repositories before job creation

[Tavomex1]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Configuration

Discussion Details

We are seeing a reproducible GitHub Actions pre-job failure across multiple repositories in the same organization.

Repository 1 — receptia-dev/Orx

Orphan/deleted workflow:
workflow_id: 351364211
path: BuildFailed
name: ""

Representative run:
34015700770

Signature:
conclusion: startup_failure
jobs: 0
no runner allocation
no checkout
no workflow steps executed

A new branch from current main containing only a minimal one-job echo workflow reproduced the same failure:

Diagnostic PR: #103
Diagnostic commit: 118be139d027ab51b185da9334db3bbf58fce7c2
Diagnostic run: 34037303887

The minimal workflow still resolved to deleted/internal workflow 351364211 / BuildFailed.

Repository 2 — receptia-dev/Cntrl

We then reproduced the same pattern independently with a different workflow registration:

workflow_id: 351342327
path: BuildFailed
name: ""

Runs:
34013098533
34039937820
34039944869

All terminate with:

startup_failure
jobs: 0

Importantly, on the same CNTRL commit where GitHub Actions failed pre-job, the Cloudflare GitHub App successfully received the repository event and completed its check. This suggests repository event delivery itself is working.

Workflow YAML was validated, and the Orx minimal reproduction rules out checkout, tests, secrets, runner labels, workflow permissions, and repository-specific workflow complexity.

We therefore suspect stale/orphaned GitHub Actions workflow-registration metadata in the event-dispatch layer.

There does not appear to be a documented self-service method to purge/reindex this internal registration.

Questions:

Is this a known GitHub Actions backend issue?
Is there a supported self-service method to rebuild/reindex workflow registration metadata?
If not, what is the correct path for getting this platform state escalated to GitHub engineering when the account does not include direct technical support?
We can provide additional REST API output and exact reproduction steps if useful.

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