Troubleshooting
Common errors
The messages you are most likely to see, what they mean, and how to fix them.
Before a run
| You see | Fix |
|---|---|
| Choose a project from the left sidebar before sending a message. | Select a project in the Projects panel, then send again. |
| Add your … API key in Settings to unlock this model. | Add that provider's key, or pick another model. See API keys. |
| Select a project before connecting a connector | Open a project first; connectors belong to a project. |
| Connection failed (Local models) | The server must be reachable from the internet, at a public address. See Local models with Ollama. |
| Only an organization admin can change skills. | Ask an admin to add or change the skill. |
During a run
| You see | Fix |
|---|---|
| A step fails while reading or writing a system | Check the connector's credentials, that the host is reachable, and that the user can read or write the schema. Update the connector from Connectors → Connected. |
| Connector id … is not registered | The connector was disconnected or belongs to another project. Connect it in this project and run again. |
| A step keeps failing after retries | Open its console for the error, then tell Auprimus what to change or edit the script. See When a step fails. |
Scheduled runs
| You see | Fix |
|---|---|
| Scheduled run failed, naming steps without a script | Run the workflow once by hand so every step saves its code. See Schedules. |
| A run stopped at a limit | It passed a token, cost or time cap you set on the schedule. Raise the cap in the schedule's Guardrails or Resilience tab. |
Still stuck? See Contact support.
Something wrong or missing? Write to [email protected] about “Common errors”.Updated 26 Sep 2026