Build & integrate
Developer troubleshooting
The first-pass diagnosis path for CALIBER SDK and REST integrations: auth, project scoping, CSRF, uploads, waiters, and workflow invocation.
Use this page for first-pass developer diagnosis across SDK and REST usage: auth, project scoping, CSRF, uploads, waiters, and workflow invocation.
At a glance
| Symptom | First thing to check |
|---|---|
| SDK call authenticates but sees the wrong objects | project scope/header alignment |
| Browser write works but automation fails | auth model and CSRF expectations |
| Raw HTTP works but SDK code fails | client configuration or version mismatch |
| Upload or file-backed workflow calls fail | workflow storage and media constraints |
| Long-running operation never settles | use the documented waiter/polling path |
| Workflow invocation fails after compile | runtime inputs, downstream tools, or approvals |
1. Auth and scope issues are the most common root cause
Before debugging business logic, confirm:
- base URL
- bearer token or session model
- project scope
Use Auth and project scoping for the canonical first-pass checklist.
2. Keep browser and automation contracts separate
The browser flow may involve session and CSRF behavior that your service integration should not copy unless you are intentionally emulating the UI.
3. Use the right surface for the question
| If the question is... | Use this next |
|---|---|
| what route family exists? | Resource catalog |
| what exact method or model exists in Python? | SDK API reference |
| what runtime path does a workflow use? | Workflows |
| why is the operator runtime degraded? | Operator troubleshooting |