Can't trigger any manual workflows

[LostRuins]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Misc

Discussion Details

I have my github actions unmodified, but since today I cannot trigger the workflow manually anymore. Clicking the green "Run Workflow" button does nothing. This affects all my workflows. Anyone else have the same issue?

Example:

Clicking the green "Run Workflow" button does nothing, no error.

I was hoping to do a release today, hope this gets fixed soon

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

[LeftMonster]

same here +1
It seems to the frontend issue?

[pakeke-constructor]

I am getting this too. on workflow_dispatch.
The button appears but it doesn't work.

Agree, looks like a frontend issue?

[anthonygacis]

Same here

[pakeke-constructor]

For context I've tried clearing the cache, disabling all extensions, using a different browser, and renaming the workflow.
(No improvements, still broken)

[avengerx]

This looks like a general issue.
To add a bit more context this is happening both to repositories introducing new workflows or repositories that already had workflow_dispatch workflows logged.

[NishuRajput12]

Hey everyone 👋
This seems to be a current GitHub Actions UI bug.
A few things you can try while GitHub fixes it:
• Clear browser cache or use Incognito mode
• Try a different browser (Chrome/Firefox)
• If that still fails, use the REST API to trigger your workflow manually:

curl -X POST \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR_TOKEN>" \
https://api.github.com/repos///actions/workflows/.yml/dispatches \
-d '{"ref":"main"}'

This should trigger the same workflow even when the UI button is broken.
Hope this helps! 🙌

[Setmaster]

Spent half an hour trying to figure out what's wrong on my end, good to know it's on GitHub's.

[nanasi880]

|￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣|
| Don't Push To Production On Friday   |
|＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿|
                     \ (•◡•) / 
                       \      / 
                        ——
                        |     |
                        |_   |_

Due to the feature breaking unexpectedly, I was required to respond during my lunchtime on a day off.
At a minimum, failures should be surfaced—for instance by emitting exception logs—so it’s clear the system is in a broken state. Since operations were silently dropped, we had to monitor to figure out whether jobs were simply delayed or not being processed at all, which prolonged recovery.

[rspears74]

Spent a long time scratching my head about this. Working from Github Mobile!

[daesu]

Same here. This is quite frustrating.

[robin-thomas]

You can trigger the workflow using GitHub API.

curl --location 'https://api.github.com/repos/{OWNER_NAME}/{REPO_NAME}/actions/workflows/{WORKFLOW_FILE_NAME}/dispatches' \
--header 'Accept: application/vnd.github+json' \
--header 'Authorization: Bearer <GITHUB_PAT>' \
--header 'Content-Type: application/json' \
--data '{
    "ref": "{BRANCH_NAME or TAG_NAME}",
    "inputs": {
        ... if you need to pass any inputs to the workflow
    }
}'

---

If you want to deploy a branch (and not tag), GitHub mobile also works.

[R055A]

I am experiencing the same issue for approximately the past hour

[LostRuins]

it is our halloween weekend present. spooky!

edit: I was finally able to trigger the workflows by downloading the Github android app. That seems to be the easiest workaround for now. I'm sure the API curl method works too, but it's a bit too janky to use with so many different workflows.

[pakeke-constructor]

I don't think this should be marked as an answer lol, there is still clear bug in github

[LostRuins]

True it's more like a workaround that works for me. But I agree we need a proper fix

[R055A]

FYI, GraphQL explorer is scheduled for removal from API doc today

[iryndin]

The same issue for the past hour.

[CatBraaain]

As workaround:
The GUI click trigger is successful in vscode with vscode-github-actions extension.

[lennardkorte]

life saver! Thanks man!

[chetanbothra]

i have to use mobile app to get my workflow running !!!

[R055A]

I am now again able to manually run workflows on the GitHub website

[NishuRajput12]

1️⃣ Short-term solutions (to get your workflows running now)

Use the GitHub mobile app: Install GitHub on Android or iOS and trigger the workflow from there.

Use the REST API (manual trigger): Run your workflow using a curl command:

curl -X POST
-H "Accept: application/vnd.github+json"
-H "Authorization: Bearer <YOUR_TOKEN>"
https://api.github.com/repos///actions/workflows/<WORKFLOW_FILE>.yml/dispatches
-d '{"ref":"main"}'

Replace <YOUR_TOKEN> with your GitHub Personal Access Token

Replace with the repository owner

Replace with the repository name

Replace <WORKFLOW_FILE> with your workflow filename

"ref":"main" is your branch or tag name

Use VSCode extension: If you use VSCode, the GitHub Actions extension allows you to trigger workflows directly from the editor.

2️⃣ Browser fixes (if you want to try web)

Clear browser cache or try Incognito mode

Try a different browser (Chrome, Firefox, Edge)

Temporarily disable browser extensions

3️⃣ Long-term

This is a GitHub frontend bug. They will fix it in a future update.

Until then, mobile app or API is the most reliable workaround.