GitHub Actions startup_failure before job creation despite passing actionlint #212770
Replies: 3 comments
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
I saw a similar failure on November 11 in a public repository. My manually triggered Public run: https://github.com/markkoehn0/btlb-feed-monitor/actions/runs/43095789756 Is there a way to retrieve the startup diagnostic for an existing run when no job logs were created? |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
Issue description
I'm experiencing a GitHub Actions issue in a private repository.
A manually triggered workflow fails with
startup_failurebefore any jobs are created.GitHub displays:
However, no specific validation error, failed line, or actionable diagnostic is provided.
Environment
workflow_dispatchubuntu-lateststartup_failureAn earlier revision of the same workflow successfully created and executed jobs. The failing revision includes modifications to job steps, diagnostic reporting, and artifact handling.
The workflow still uses the same manual trigger, job configuration, permissions, and runner type.
Troubleshooting already performed
The following checks passed:
actionlint v1.7.12on both the previously working revision and the failing revision, with zero errors.Repository settings were also verified:
The account also had remaining included GitHub Actions compute credit.
An Actions spending budget of $0 is configured with usage blocking enabled to prevent additional charges. It is unclear whether this setting could affect job creation despite available included compute.
Questions
startup_failurebefore a job or check run is created, even whenactionlintpasses?Additional information
For privacy and security reasons, I have intentionally omitted repository identifiers, workflow URLs, commit hashes, and application-specific details from this public discussion.
I can provide the exact run identifiers and other relevant technical metadata to authorized GitHub staff through an appropriate private support channel.
I would prefer not to disable spending protections or trigger additional runs without understanding the root cause.
Thank you for any guidance.
All reactions