Troubleshoot common problems
On this page
Start with the exact failing request, environment, and time. Identify the layer that rejected or failed the request before changing workflow behavior.
Route and access problems#
| Symptom | Check first |
|---|---|
| 404 / endpoint not found | Controller path, action route, HTTP method, environment, production release availability |
| 401 | Gateway credentials and IdP bearer token requirements; internal test bypass versus public request |
| 403 | Key scope, role/permission gate, CORS, country/IP rules |
| Signature rejected | Millisecond timestamp, clock drift, exact method/path/query/body bytes |
| Browser fails but server client works | Browser Origin, preflight, tenant API hostname, credentials mode |
| Limit-related rejection | Key request limits, account limits, selected environment |
See API access, signing, and CORS for focused checks.
Workflow problems#
A node never runs: inspect the entry node and execution connections. Check whether an earlier node failed or a branch selected another path.
A selector is empty or wrong: check its spelling, controller/global scope, environment, and the point where it is produced. A result on another branch may not exist in this run.
Python cannot read an upstream result: reference its selector directly, such as customer = ${FetchCustomer}. A bare name like FetchCustomer is not a Python global. Check that the producing node ran and that its result has the expected shape.
SQL fails: confirm the database binding, SQL dialect, schema, parameter names, and input types. Test a read-only query before retrying a mutation.
A schedule does not run: inspect its state, timing/timezone, environment, target action, and resulting logs. A Schedule node configures a later job rather than calling the target inline.
App problems#
An empty widget with a successful request often has the wrong data path or response shape. A direct page URL failing after refresh points to routing or publication configuration. A newly published app calling an older API contract needs release/dependency review.
When to open a ticket#
Include expected and actual behavior, reproduction steps, environment, time with timezone, action/app, relevant version, and a specific log reference. State what you have already checked. Follow evidence guidance before attaching payloads.
Need to investigate a problem? Start with troubleshooting