Errors
Failed HTTP calls return:
{ "error": { "code": "event_mismatch", "message": "..." } }@trigora/client throws TrigoraRuntimeError with status and code. The Python client raises TrigoraError the same way. The CLI prints the message.
| Code | When |
|---|---|
unauthorized | Missing or rejected Cloud token |
forbidden | Token cannot access the project |
not_found | Generic missing resource |
program_not_found | start or deploy target missing |
project_not_found | X-Trigora-Project-Id is unknown |
execution_not_found | Bad execution id |
execution_not_waiting | Send or a wait operation against an Execution that is not waiting |
event_mismatch | Event name does not match the current wait |
execution_not_cancellable | Cancel is not valid for this status |
invalid_input | Body failed validation |
bad_request | Malformed request |
conflict | State conflict |
compiler_failed | Frontend rejected the Program |
rate_limited | Too many requests |
internal_error | Host or API failure |
The compiler_failed code indicates that the Program did not compile. Update the source to use supported language semantics and compile it again; recovery is not involved. See Unsupported constructs.
A missing TRIGORA_TOKEN on a Cloud CLI command fails in the CLI before HTTP, with TRIGORA_TOKEN is not set.