Troubleshooting

Fixes for runs that will not start, time out or keep coming back flaky.

Most failed runs come from the environment, not from AMI. Start with the first error in the run log, then check the matching section below.

AMI cannot reach the app

Check that the app is running and that API_URL in your env file points at it. In CI, wait for the app to be ready before the run starts.

bash

npx anthivo run --env .env.test --verbose

A 401 means the key is missing or wrong; a 429 means you hit a rate limit. Lower ami.agents, or raise the limits on your provider account.

Long suites can exceed the default timeout. Split them across runs, or enable fewer suites on pull requests and run the rest nightly.