Operating
Troubleshooting
What common errors mean and where to look
API errors come as application/problem+json, with the reason in detail.
API
| Answer | Cause |
|---|---|
401 | The Authorization: Bearer <token> header is missing or does not match OPERION_API_TOKEN |
400 with X-Tenant-Id header is required | Workflow and execution routes need the tenant header |
404 on a workflow or execution | It does not exist, or it belongs to another tenant |
422 on publish | The workflow cannot run; detail lists every problem. See publishing |
400 on resume | The node is a remote node waiting for its callback, and the body has no port; send the answer, {"port": "<output>", "data": {...}} |
409 on resume | The node is not waiting, or it was already resumed |
Workflows that do not start
- Webhook answers
404. No published workflow of that tenant listens on the path. Check that the workflow is published, that the tenant in the URL is the workflow's tenant, and that the path after the tenant equalswebhook_path, leading/included. - Catalog event does nothing. Check that
servehas--kafka-brokers, that a published workflow uses the event, and the logs forevent skipped: the message could not be decoded, had no tenant attenant_key, or isavroorprotobufwithout--schema-registry-url. A new consumer group starts at the end of the topic, so earlier messages are not read. - Schedule does not fire. Only published workflows fire, and times follow the node's
timezone, which defaults to UTC.
Executions
- The execution is
failed.error_messagenames the node and the reason, and that node's entry innode_resultshas the details. Connect the node'serrorport to handle the failure instead. - A template renders
<no value>. The path does not exist in the data; compare it withnode_resultsin the execution. See templates. - A remote node fails with
remote node answered 202 but serve has no --public-url. SetOPERION_PUBLIC_URLto an address the service can reach. - A remote node fails with
remote node did not call back before its deadline. The service did not post tocallback_urlbeforeanswer_by. - The execution stays
running. A node iswaitingorretrying; its entry innode_resultssays until when.