pull_request workflows are not triggered and stale runs cannot be cancelled

[wkamer]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Workflow Configuration

Discussion Details

Hello,

I’m experiencing a GitHub Actions issue in a private repository.

New pull requests are created successfully, but the configured pull_request workflows are not triggered.

Affected pull request:

• PR #273
• Base branch: dev
• Head branch: agent/fine-grained-promotion-checks
• Commit: b401b1945f08c8dec7c7321e5a4938f080dbea11

The following workflows are enabled and active:

• Frontend validation
• Go race test
• Branch promotion contract

Troubleshooting performed:

• Created a new branch and pull request.
• Closed and reopened the pull request several times.
• Created another pull request with the same result.
• Tested both a fine-grained PAT and a classic PAT.
• Confirmed the pull request is from the same repository, not a fork.
• Confirmed the workflows are enabled.
• No workflow run is created; GitHub reports “no checks reported”.
• Self-hosted runners are online.

There are also stale workflow runs from August 26 that remain permanently queued:

• Run 32985436753
• Run 32985408043
• Run 32985254923
• Run 32985094331
• Run 32985091932

Cancellation returns HTTP 409, and deletion returns HTTP 403, including with a token that has Actions write permission.

Could someone help determine why the pull_request events are not generating workflow runs and whether the stale queued runs can be removed?

The repository is private, so I have intentionally omitted its URL and name. I can provide private details if required.

No secrets or access tokens are included.

Kind regards,
Walter Kamer

[yapcent]

Hi Walter,

It sounds like the issue may be related to how the pull_request trigger is configured or to a problem with the repository's GitHub Actions state.

Since you have already confirmed that the workflows are enabled, the PR is from the same repository, and the runners are online, I would recommend checking the following:

• Make sure each workflow has the correct on: pull_request configuration.
• Check whether the workflow has branch filters that might exclude the dev branch.
• Check the repository's Actions settings to make sure Actions are allowed for the repository.
• Review the workflow permissions under Settings → Actions → General.
• Check whether there are any organization-level Actions policies affecting the repository.
• Since the old runs are stuck in the queue and cannot be cancelled or deleted, this may require GitHub Support to investigate from their side.

Because no workflow run is being created for the new PRs, while older runs are permanently queued, this doesn't appear to be simply a self-hosted runner problem.

I would recommend contacting GitHub Support and providing the affected PR and run IDs so they can check the Actions backend for the repository.