The workflow file must be committed in the default branch (master/main) if you want to use the workflow_dispatch event. Is it still present there or only on a feature branch?

Manually running a workflow - GitHub Docs

Yes, the file is at the default branch and still doesn’t show to me on the actions tab. It’s not the first time this happens to me. Looks like GitHub get into an invalid state and after that, I can’t use the manual workflow at the repository anymore.

It’s not like I can’t see the Run workflow button, I can’t see the whole workflow. The other workflows that I have at the repository are there and working fine.

Thanks. I had the same problem with not displaying the workflow button on the page. After changing the file name, it works.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        renamed:    .github/workflows/develop.yml -> .github/workflows/build.yml

May we get a notification, when this bug is fixed? It’s quite annoying. I faced it as well.

This has been fixed, if you are still seeing a problem, please let us know where.

Hey @andymckay !
It happened just today in my private repository. I have pushed there a copy of the public repository with already existing workflows. The workflow that was supposed to be triggered manually only wasn’t detected by Github and therefore didn’t show up in Actions tab. So, I wasn’t able to trigger it. Neither via UI, nor via REST API. I had to rename a workflow file in master to make Github notice that workflow and let me run it eventually. Renaming a workflow in a branch didn’t help.

Thank you, I’ll file an issue internally and the team will take a look.

Still couldn’t get it to work in a private clone of a private repository. I’ve tried adding a comment as @lupine86 suggested but the button still didn’t appear.

It is not working for me either! no button for the workflow is being shown.

I can confirm renaming workflow from the the orignal.yml to fixed.yml fixed it for me as well. It is then also possible to rename to the orginal.yml to have it work afterwards.

Hi @andymckay,

Seems like this issue is still exist.
If not please guide me to the possible solution for this problem.

Thanks.

Hi @andymckay,

The issue still exists. Any update?

@srinivasan-getstan, @abhinavan1812 I no longer work at GitHub, so am not able to provide much insight, sorry.

Hi everyone

Same problem here (private repo)!

Not able to see the Run Manual Workflow option even though if i give the workflow_dispatch in my yml file as attached in the below screenshot,

Let me know if iam missing anything here!!

Edit: Double-cheking the default branch fixed the problem. I thought the default branch was master but for some reason it was set to an inactive feature branch.

This very simple yaml doesn't work.

• GUI button not shown

• gh workflow run gives could not create workflow dispatch event: HTTP 422: Workflow does not have 'workflow_dispatch' trigger

• renaming the name of the yaml file didn't fix the problem

name: hello
on:
    push:
    workflow_dispatch:
jobs:
    hello_world:
        runs-on: ubuntu-latest
        steps:
            - run: echo "Hello, world!"

I changed the file name but it didn't work, but changing the name of the action solved it!

name: hello-world // change this

same thing happens for me as well on my private_repo and its quite annoying.

It is still happening workflow_dispatch. The fix was to rename the filels but the workflow that has no longer a file can't be deleted.

Stil facing this issue. Now able to trigger the actions from the UI manually

name: The Docker Build Pipeline

on:
  workflow_dispatch:
  push:
    branches:
    - 'dev-*'
    - 'qa-*'
    - 'master'
    - 'v*'

jobs:
  common-actions:
    uses: fuchicorp/common_actions/.github/workflows/build.yaml@feature/master
    secrets: inherit
 

I had to change the default branch from main to master to resolve this. Same yaml file for the workflow .

I ran into this issue today. After renaming the file, renaming the workflow name, and merging to main, the Run workflow button is available. See mikesmithgh/kitty-scrollback.nvim#102

Unfortunately, 2024 problem still exist.
It's absolutely random. Some actions not fixed even after renaming/recreation, some after several pushes and some works as expected immediately after creation...