---
title: Troubleshooting
description: What the common failures mean.
---

## `Invalid User API Key`

The key is missing, malformed, or was revoked. Check that the secret is set on the repository (or organisation) and exposed to the job.

## `[plan_required] ... not available for free users`

The key is valid but the account cannot run agents. This is billing, not configuration: nothing in the workflow will fix it.

## A model id is rejected

Start from `default`. The SDK rejects `auto`, and the error lists the ids your account can actually use. `model` is passed through untouched.

## The step timed out or failed

Check the job summary. When a run reports `cancelled` (including timeout-triggered cancellation) or `error`, the action exits with code `1`. If an agent does not support cancellation, it may finish with exit code `0`. You can increase `timeout` if the agent needs more time to complete.

## `Cannot find module`

The action failed to install its own dependencies, which points at the runner's network or a corrupted npm cache rather than at your workflow. Re-run the job; if it persists, open an issue with the full step log.