Failure, notice and skip codes
Every code a failed or skipped run shows, with its exact message, what causes it and how to fix it.
When a run fails, the step fails with a message that says what to do. The job summary shows a card with the failure's code, the same message and, when there is one, a link to where to fix it. When a review fails, the pull request's summary comment shows the card too.
Parts of a message in angle brackets, such as <minutes>, are filled in by the run.
Codes from the Axon Shaft API
The action asks the API for its run before anything else, so these show before any review starts.
not_installed
Install the AxonShaft GitHub App on this repo, then re-run the job.
The AxonShaft app isn't installed on the repo, or the installation doesn't include it. The card links to the install page. Install the app on the repo, then re-run the job.
not_a_project
Add this repo as a project on the Axon Shaft dashboard, then re-run the job.
The app is installed, but nobody has added the repo as a project. The card links to the page to add it. Someone with admin rights on the account, or the Admin or Maintain role on the repo, adds it on the dashboard.
no_claude_token
Save a Claude token for this project or its account on the Axon Shaft dashboard, then re-run the job.
Neither the project nor its account has a Claude token. Save one on the project's Claude token page or the account's settings. See Claude tokens.
oidc_invalid
Re-run the job: its OIDC token was invalid, expired or already used.
The API refused the run's OIDC token because it was bad, had expired, or had been used already. Re-running the job gets a fresh one.
event_not_allowed
Run Axon Shaft from one of these events, not
<event>: pull_request, pull_request_target, issue_comment, pull_request_review, pull_request_review_comment, workflow_dispatch.
The workflow ran on an event the API doesn't take. Use the triggers in the workflow file.
rate_limited
Re-run the job in
<seconds>seconds: this repo called the Axon Shaft API too often.
The repo went over a rate limit. Wait the time the message gives and re-run the job. Limits has the numbers.
api_error
Re-run the job in a few minutes: the Axon Shaft API had an error.
Something on the API's side failed, such as GitHub or the database, or the API's answer couldn't be used. The action sends the same code when the API answered with an error page or an incomplete answer, or with a setting it can't run with. In that last case the message names the setting and links to the dashboard. Re-run the job in a few minutes, and check the repo's settings if the message names one.
Codes from the action
missing_id_token
Add
permissions: id-token: writeto the workflow, so Axon Shaft can fetch its tokens from its API.
The workflow has no id-token: write permission, so the action can't get the run's OIDC token to sign in. Add it under permissions:, as in the workflow file.
api_unreachable
Couldn't reach the Axon Shaft API at
<url>(<error>). Rerun the job in a few minutes.
The action couldn't reach the API, or the API took over 30 seconds to answer. Re-run the job in a few minutes.
review_timed_out
The
<review, reply or task>ran past its<minutes>-minute time limit. Raise the time limit on the dashboard, or rerun the job.
The run went past the account's time limit, 15 minutes unless it's changed. The card links to the dashboard. The account's admin can raise the time limit.
review_invalid_reply
The model's reply didn't match the
<review, reply or task>format twice, so nothing was posted. Rerun the job; both replies are in the job log.
The model's answer didn't match the format the action reads, on both tries, so nothing was posted. The card links to the run. Re-run the job.
review_failed
The
<review, reply or task>failed:<reason>. Rerun the job; the job log has the details.
The run stopped for another reason, such as an Agent SDK error or the turn limit. The card links to the run, and the job log has the details. When the turn limit is the cause, the account's admin can raise the turn limit.
push_failed
/fix or /axonshaft couldn't push its commit, and the message says why. The causes:
- the project's push mode rules out the branch;
- the pull request's branch is on a fork, or is the default branch;
- the change touched
.github/; - the installation hasn't approved the app's Contents (write) permission;
- GitHub refused the push.
Nothing is changed on the branch. Fix the cause the message names and comment the command again.
self_hosted_unsupported
Axon Shaft makes changes only on GitHub-hosted runners, and this job runs on a self-hosted one, so nothing was changed. Run the Axon Shaft job on
runs-on: ubuntu-latest.
/fix and /axonshaft ran on a self-hosted runner. They run only on GitHub-hosted runners, so no session ran. The run ends with a notice and the step passes.
credentials_in_checkout
The checkout's .git/config holds a GitHub credential, which the model could read, so nothing was changed. Set
persist-credentials: falseon the workflow's actions/checkout step.
/fix or /axonshaft found a token in the checkout's .git/config, so no session ran. Set persist-credentials: false on actions/checkout. The run ends with a notice and the step passes.
sandbox_unavailable
/fix or /axonshaft couldn't start the sandbox its commands run in on this runner, so no session ran. The message says why. Run the job on ubuntu-latest, where the action installs the sandbox when it's missing. The run ends with a notice and the step passes.
claude_binary_unverified
The action downloads Anthropic's Claude Code binary from npm at the version its release pins, and runs it only if its sha512 matches the hash the release records. This one didn't match, or the release records no hash for the runner's platform, so it never ran and nothing was reviewed or changed. Rerun the job: a download that broke on the way gets a fresh copy. If it fails again, pin the workflow to the latest axonpack/shaft-actions release and tell us, because a mismatch on a clean download means the package on npm isn't the one the release was built with.
Cancelled runs
A cancelled run posts no review. The dashboard shows it as Cancelled, and the usage totals count it as failed.
cancelled
The workflow run was cancelled before the review finished: someone pressed Cancel, a newer push replaced the run through the workflow's concurrency setting, or the job hit GitHub's own time limit. Axon Shaft closes every check run it opened as cancelled and shows this notice in place of the reviewing message, so nothing stays in progress. Push again, or comment /review, to start a new review.
Runs that end with a notice
These runs post no review, and the step passes with a notice that gives the reason.
nothing_to_fix
The last review has no open findings to fix.
or, before any review:
There's nothing to fix yet: comment
/reviewfirst.
A bare /fix takes the open findings of the last review, and there were none. Comment /fix <what to change> instead, or /review first.
spending_cap
Axon Shaft reached
<this repo's or the account's>monthly spending cap, so nothing runs until the 1st (UTC). An admin can raise the cap in the settings on the Axon Shaft dashboard.
This month's runs on an API key cost as much as the project's or the account's monthly cap. Nothing runs until the 1st of next month (UTC), or until the account's admin raises the cap.
pull_request_limit
This pull request already started 10 /ask and /fix runs this hour, the most one pull request may, so this one wasn't started. Try again in
<minutes>minutes.
Each pull request may start 10 /ask, /fix and /axonshaft runs an hour, so one person's repeated commands can't spend the project's Claude budget. The count starts again at the top of each hour (UTC). Reviews don't count and aren't held back, and refused commands don't count.
fork_pull_request
PR #
<number>is from a fork, and a fork's pull_request run gets no OIDC token. To review it, run the workflow on pull_request_target.
GitHub gives a fork's pull_request run no OIDC token, so the action can't sign in to the API. Run the workflow on pull_request_target, as in the workflow file. The project's forks setting then decides whether a fork's pull request is reviewed.
not_a_pull_request
/<command>works on a pull request, not an issue.
/review, /ask, /fix or /axonshaft was commented on an issue. Comment it on a pull request instead.
no_write_access
<login>has no write access, so no review was started. Only people with write access can start one with /review.
The commenter has no write access to the repo, and only people with write access can start a run. The end of the message follows the command: after /ask the question isn't answered, and after /fix or /axonshaft nothing is changed. Ask someone with write access to comment the command.
paused
Axon Shaft is paused on this repo. An admin can resume it in the project's settings on the Axon Shaft dashboard.
An admin paused Axon Shaft on the repo, so nothing runs, not even /help. The account's admin, or someone with the Admin or Maintain role on the repo, resumes it in the project's settings.
skip_label
<automation>skips pull requests labelled "<label>" on this project. Someone with write access can comment /review to review it anyway.
The pull request has one of the labels in the project's skip labels. Remove the label and push, or comment /review to review it once.
filtered
<automation>doesn't review pull requests opened by bots (<login>) on this project.
One of the Code review's filters skipped the pull request, and the message names which: Axon Shaft's own pull requests, bots, outside contributors, or a branch it isn't set to review. Someone with write access can comment /review to review it anyway.
Notices without a code
The run also ends with a notice, and no card, when:
- Code review is off on the dashboard, or the event isn't one of its "When it runs" choices;
- the pull request is from a fork and the project's "Pull requests from forks" setting holds it back.
Someone with write access can comment /review to review a pull request that the fork setting skipped.
Warnings that don't fail a run
advisory_failed
Axon Shaft couldn't open a private draft security advisory for a blocking security finding, for example because the project's advisories setting is off for this repo or the installation hasn't approved Repository security advisories (write). The review posts the finding as it is.
code_quality_failed
Axon Shaft couldn't read GitHub Code Quality's findings, usually because Code Quality isn't on for the repo or the installation hasn't approved Code quality (read). The code-quality checklist is skipped, with the message as the reason.
packages_check_failed
The Axon Shaft API looked up no package for the Known vulnerabilities or Licences checklist: osv.dev and GitHub's advisory database both failed, the run has no open review, or a name wasn't a public package's. The checklist is skipped, with the message as the reason.
Last updated on