GitHub Actions GITHUB_TOKEN cannot trigger another workflow

By Kaveh Alemi·Latchkey

GitHub intentionally does not run workflows from events created with the GITHUB_TOKEN, to prevent recursive runs. Your downstream workflow simply never starts.

What this error means

A commit, PR, or dispatch made by a GITHUB_TOKEN step does not trigger the workflow you expected to follow it.

# Push made with secrets.GITHUB_TOKEN: no new workflow run is created
# (no error is shown; the expected downstream run is just absent)

Common causes

Loop prevention by design

Actions skips triggering new runs from token-authored events to avoid infinite loops.

Expecting a chained workflow

A push or dispatch from CI was assumed to start the next workflow, but it does not with the default token.

How to fix it

Use a PAT or App token to chain workflows

1. Make the triggering event with a PAT or GitHub App installation token instead of GITHUB_TOKEN.
2. Or use workflow_run / repository_dispatch to chain deliberately.

- uses: actions/checkout@v4
  with:
    token: ${{ secrets.CHAIN_PAT }}

How to prevent it

• Decide explicitly whether chaining is intended and use a suitable token.
• Prefer workflow_run for controlled, loop-safe chaining.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions