GitHub Actions: No run after manual dispatch #213174
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. ⭐ |
|
A good first check is whether GitHub recorded anything at all, without triggering it again. In the repository, open the Actions tab and use the workflow filter for this exact workflow, then also check the run list with the GitHub CLI using gh run list for that workflow. If both show nothing, the dispatch likely never created a run. Common causes are a YAML problem on the default branch, a workflow_dispatch input that does not match the inputs defined in the file, or the workflow being disabled in the repository Actions settings. Check that the file on the default branch has the dispatch trigger and the same two required inputs, and check the GitHub status page for an Actions incident around 03:44 UTC. If the file looks correct, the repository audit log can also show whether the dispatch event was recorded. |
|
Hi @stevenai2026, I can't see GitHub's backend, so I can't confirm whether your dispatch was received. Here is how to check without triggering the workflow again, and what commonly causes this. Checking whether the dispatch was received (no re-run)
If none of these show a run, the request most likely never created one. Retrying is then reasonably safe, though if your workflow has side effects (deploys, releases, writes), make sure it's idempotent or confirm in the API first. Known causes of "dispatch seemed to work but nothing ran"
If nothing explains it Open a ticket at https://support.github.com/contact with the repo owner/name, the exact timestamp (03:44:10 UTC), the workflow path, and the inputs you used. Staff can search server-side logs for the dispatch request, which you can't. Please don't post the repo name publicly. Hope this helps! |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
Hello GitHub Community,
I’m experiencing an issue with manually triggering a GitHub Actions workflow using workflow_dispatch in a private repository.
The workflow is on the default branch and has a workflow_dispatch trigger with two required inputs.
On November 15, 2026, at 03:44:10 UTC, I selected the correct branch, entered both inputs, and clicked the final “Run workflow” button once.
The submission form closed, but no workflow run appeared.
Approximately 18 minutes later:
The workflow YAML has been deployed and its commit and file hash were independently verified. The earlier unrelated workflow successfully ran in the same repository.
I have not retried the dispatch because I cannot confirm whether GitHub received the original request.
Could anyone explain how to determine whether the UI dispatch request was received or rejected, preferably without triggering the workflow again?
Are there known issues or repository settings that could cause this behavior?
Thank you.
All reactions