Troubleshooting
Error messages and connection problems, with the fix.
This section is for the moment something does not work: an error message in the terminal, an agent that cannot see its solution, a pull or merge request that fails the change-request check, test results that never reach the criteria. Each article starts from the symptom, explains why it happens and ends with the fix.
Most connection problems come down to identity. A token was revoked or expired, a sign-in was never completed, or the person behind the connection lost access to the solution. The first articles cover those, including what 401 invalid_token means and why Claude Code may show the server as failed.
Other problems are about rules working as intended: a proposal refused because the connection is read-only, an action refused for lack of permission, a pull or merge request that cites no record, a work item refused because its initiative answers no demand. The refusal usually says which permission is missing and who holds it.
If your problem is not an error but an agent doing the wrong thing, look in “When things go wrong” instead; if you still cannot find it, write to us with the solution, the time and what you saw.
Articles in Troubleshooting
- Troubleshooting401 invalid_tokenCorPole refused the agent's credentials. The token is revoked or expired, the solution is not active, or its owner can no longer read the solution.
- TroubleshootingClaude Code shows corpole as failedThe MCP server is listed but not connected. Usually Claude Code has neither a token nor an OAuth sign-in for it.
- TroubleshootingThe agent's proposal was refusedpropose_record and the other write tools need the propose permission. A read-only connection can read everything its owner can, but cannot propose.
- TroubleshootingMy agent ignores the requirementsThe agent writes code without reading CorPole, or follows a file in the repository instead. Most often the repository does not tell it that CorPole comes first.
- TroubleshootingMy agent sees the wrong solution, or noneEvery connection belongs to exactly one solution. The agent sees the solution its token was created in, or the one chosen on the OAuth consent screen.
- Troubleshooting"You don't have permission"CorPole refused an action because you, or the person your agent acts for, lack the permission. The message names the permission, who holds it and where it is done.
- TroubleshootingThe change-request check fails (GitHub, GitLab)The CorPole check wants every pull request (GitHub) or merge request (GitLab) to cite at least one existing, non-retired record code.
- TroubleshootingTest results don't show up on the criteriaA criterion follows the test cases linked to it. If results do not arrive, the test is not linked, or its automation reference does not match what CI reports.