GitHub Actions runs fail instantly with “startup_failure” and no job

[seb1-web]

Hello,

I need help with a GitHub Actions issue affecting my private repository:

Repository: seb1-web/global-auto-atlas

Default branch: main

Every push creates a workflow run that fails immediately before any job or runner starts.

Latest affected run:

https://github.com/seb1-web/global-auto-atlas/actions/runs/33738476467

Observed details:

• Run ID: 33738476467

• Commit: 78a265f9d8dd92284850e95140679b86e2f15530

• Event: push

• Status: completed

• Conclusion: startup_failure

• Workflow ID: 343520410

• Workflow name: empty

• Workflow path: BuildFailed

• Jobs: 0

• Logs: none

This is not limited to the latest commit. The same failure occurred on every push since the repository was initialized:

• Run 33045733400 — commit a260627

• Run 33051581916 — commit 59f5451

• Run 33086831959 — commit 3b9f4d0

• Run 33738476467 — commit 78a265f

The repository contains valid workflows:

• .github/workflows/ci.yml — named “CI”, triggered on pushes to main and pull requests

• .github/workflows/smoke.yml

The failing runs do not reference either workflow file. Instead, they reference an empty workflow named “BuildFailed”, which does not exist in the repository.

I have already checked the repository’s Actions settings and Actions are enabled. The CI workflow has not been changed by the latest project work.

Could you please investigate whether there is an orphaned or deleted GitHub Actions workflow record associated with workflow ID 343520410, and clear or rebuild the workflow registration for this repository?

Thank you.

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