Common issues
Find the symptom, read the cause, apply the fix. Deeper: runner troubleshooting and publishing and measurement.
| Symptom | Most likely cause | Fix |
|---|---|---|
| Cannot sign in | The invitation link has already been used | Sign-in |
| The runner sits at “Waiting for approval” | Nobody has approved the code | Pairing |
| A run never leaves pending | No runner is connected, or none has the right coding agent | Runs |
| The wizard or a task says the runner is not signed in | The runner has no sign-in for that coding agent | Sign-in |
| Agent features fail with “no runner connected” | The workspace is on the runner backend with nothing paired | Runs |
| A task says no runner has a language installed | No runner has the task’s toolchain | Toolchains |
| An invitation email never arrived | It is in spam, or the link was already used | Invitations |
Something spent no tokens and returned 402 | Trial credits are exhausted | Credits |
| A publish fails with “No active binding” | Nothing is connected and activated for that channel | Publishing |
| An analytics binding fails to verify | The G- measurement ID was used instead of the numeric property ID | Publishing |
Search Console answers 403 on every call | The property is entered in a form you do not own | Publishing |
| The search columns on a new article stay empty | The page is not indexed yet, and reporting lags further behind | Publishing |
I cannot sign in
Section titled “I cannot sign in”Use the address your invitation was sent to. Invitation links are single-use, so if yours was used, ask whoever invited you for another. See users and invitations.
The runner will not pair
Section titled “The runner will not pair”Work through these in order. The rest are in runner troubleshooting.
- Approve the code. The terminal prints a URL and a code. Open it, sign in if asked, and approve: the runner is waiting for a person, not the network.
- Approve in the right workspace. The code exists only in the workspace the installer paired with, the hosted CommandChain unless you passed
--server. - Codes expire after ten minutes. Re-run the installer for a fresh one.
- You already have a runner with that name. That is allowed: display names are not unique, so pairing again adds a second entry, and an admin can retire the old one once the new one is online.
- The machine cannot contain an agent. Open the runner with
commandchain-runnerfor the reason, or runcommandchain-runner doctor. This is not overridable: use CommandChain’s managed servers instead. See proving containment with doctor.
A run is stuck and never starts
Section titled “A run is stuck and never starts”A pending run is waiting for somewhere to execute. In order of likelihood:
No runner is connected. Agent actions fail with HTTP 503 and the error key no_runner_available rather than falling back to a paid API.
curl -fsSL https://github.com/commandchain-ai/commandchain-runner-dist/releases/latest/download/install.sh \ | shA runner is paired but reads offline. Runners are graded on their last check-in. Check sh install.sh --status on that machine.
No runner has the right coding agent. The run waits rather than running with the wrong one, and the error names every runtime it tried. Install that tool on the machine and restart the runner. See coding agents.
The runner is not signed in to that coding agent. See below. On managed servers, upload a login instead: open the runner with commandchain-runner and press c, or run commandchain-runner creds push.
The workspace is at its concurrency limit. A workspace runs five at once by default, and later runs queue. See limits.
The setup wizard says my runner is not signed in
Section titled “The setup wizard says my runner is not signed in”On the runner machine, open the runner with commandchain-runner: enter signs in to the suggested coding CLI, s picks another or an API key. Or run commandchain-runner signin --agent claude-code (or codex, gemini) as the user the runner runs as. The wizard moves on within a minute. See sign-in only or full setup.
A task says no connected runner is signed in to the coding agent this task needs
Section titled “A task says no connected runner is signed in to the coding agent this task needs”On the runner machine, open the runner with commandchain-runner and press s to sign in to the CLI the task’s agent uses, or run commandchain-runner signin --agent with claude-code, codex or gemini, as the user the runner runs as. With full setup on, sign in to that CLI as you normally do. The task picks itself back up once a runner is signed in, or once managed runs are turned on.
A task says no connected runner has a language installed
Section titled “A task says no connected runner has a language installed”Open the install task for that language, run its commands on a self-hosted runner’s machine, then open the runner with commandchain-runner and press r: the task starts again on its own. See install a toolchain. If you use only managed runs without that language, install a self-hosted runner on a machine that has it.
An invitation email never arrived
Section titled “An invitation email never arrived”Check spam first. Invitations are sent when created, so a missing message is almost always filtering. The link still works: whoever sent it can reopen the invite dialog, Copy it and send it directly, or re-send it. See users and invitations.
A request returned 402
Section titled “A request returned 402”Trial credits are exhausted. The request stopped before calling a model, so nothing was spent. The error key is trial_credits_exhausted.
Pair a runner, or connect your own AI credential. See trial credits.
Next steps
Section titled “Next steps”- Runner troubleshooting: every runner failure, in depth.
- FAQ: the questions before the symptoms.
- Get help: when none of this fits.