Failed to queue workflow run: Bad request - Actions has been disabled for this user.

[deep-soft]

🏷️ Discussion Type

Bug

Body

Failed to queue workflow run: Bad request - Actions has been disabled for this user.
I receive this message when I try to run one workflow from https://github.com/deep-soft/far2l.
I checked "Actions permissions" for this repository, and the "Allow all actions and reusable workflows" is selected.
Also in Runners there are no Github-hosted runners.
I believe Actions are disabled for Account, so for all repositories.
Please, someone, advise where to apply for restriction removal.
Thank you.

[NspxMiguel]

That message is different from a repository's normal Actions policy. GitHub's documentation explicitly says that when Actions is in a GitHub-controlled disabled state for the account, changing the repository's Actions permissions will not restore access; GitHub Support has to review it.

Open a ticket through the GitHub Support portal while signed in to the affected account. Include:

• the exact message: Failed to queue workflow run: Bad request - Actions has been disabled for this user;
• the affected username and repository/workflow URL;
• the approximate UTC time of the failed dispatch;
• confirmation that Settings → Actions → General → Allow all actions and reusable workflows is already selected;
• whether the same error occurs in a small repository owned by that account.

There may be no workflow-run URL or logs to attach because the request is rejected before a run is queued; say that in the ticket. The empty GitHub-hosted runners list is not evidence of a missing runner registration—persistent entries on that page are for self-hosted runners, while GitHub-hosted runners are assigned when jobs queue.

The relevant GitHub note is under Managing GitHub Actions settings for a repository, and GitHub also lists the information Support normally requests in Getting help with GitHub Actions.

I would not change the workflow YAML or install a self-hosted runner for this error: neither can bypass an account-level disabled state.

[deep-soft]

Thank you, for your comment.
In the meantime I successfully one create ticket (at support) and resolved this issue.