> For the complete documentation index, see [llms.txt](https://kerno.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerno.gitbook.io/docs/troubleshooting/test-execution-issues.md).

# Test Execution Issues

### My test run looks stuck

The most common cause is not a stuck run at all: it is a run waiting for you.

When Kerno pauses to ask for plan approval or for an answer, the job keeps reporting as running. Job status does not surface these gates. Ask your agent to check for pending Kerno feedback, and answer it.

If nothing is pending, check the job's log path for the last activity, or ask your agent to cancel and start again.

### Kerno says there's nothing to validate

Validation runs the scenarios already on disk for an endpoint. If none exist, the run stops immediately and tells you to generate first. Nothing is created implicitly.

Generate tests for that endpoint before validating it.

If you asked "what did my changes affect?" and got nothing back, check whether your changes are still uncommitted. The `changed` scope compares your working tree against `HEAD`, so once everything is committed there is nothing in the diff. Target the endpoint or file directly instead.

### Tests are failing with 401s or 403s

Kerno works out how each endpoint authenticates by reading your source. When it gets this wrong, every scenario fails at the door.

* Check whether your auth needs a credential Kerno cannot obtain by itself. If your app signs tokens with a secret from an environment variable, provide it so Kerno can construct a valid token.
* Tokens Kerno signs itself use HMAC algorithms. If your verifier requires `RS256` or another asymmetric algorithm, Kerno needs a real login endpoint to call instead.
* Flows requiring a person to complete a hand-off with an external identity provider cannot be automated. Those scenarios report as blocked.

### A scenario reports as blocked

Blocked means the scenario could not run, usually because a dependency it needs is not configured. It is neither a pass nor a fail. See [Environment Setup Issues](/docs/troubleshooting/environment-setup-issues.md).

### A scenario reports as not implemented

Kerno could not produce a working scenario for that case. This is reported honestly rather than counted as a pass. Try running an update on the endpoint with guidance describing what that scenario should do.

### Kerno flagged a "potential bug" that isn't one

Potential bugs attach to scenarios that pass: Kerno found the endpoint doing something the plan did not expect and documented the real behaviour.

If it is known or intended, tell your agent to ignore it. Kerno records the decision for that endpoint and stops flagging it. Note that there is currently no way to reverse this through Kerno.

### My endpoint changed on purpose and now everything fails

That is working as intended. Run an update rather than regenerating:

> "Use Kerno to update the tests for POST /users — the response no longer includes the role field."

Update keeps every scenario that still applies and edits only what your change requires.

{% hint style="info" %}
If you encounter issues or have questions, [message us on Discord](https://discord.gg/k8yA9tZdP9), and we'll gladly help.
{% endhint %}