Troubleshooting
Resolve connection, input, permission, publication and rendering problems.
Start with the failing operation and its context. An unavailable API, an unauthorized record, a missing input and a valid empty query result need different fixes.
A destination works until the page is refreshed
Check that you are signed in to the same workspace and can access the destination and its dependencies directly. A deep link carries destination/input values, not another user's delegated access. Verify the current publication and required inputs.
Use the browser Network panel to identify the failing endpoint and response. Share the status, error code and request context when reporting a bug; omit cookies, tokens and confidential result rows.
A source cannot open a local session
For an SSH-discovered database, check the selected host/container, installed database client and the SSH user's ability to invoke it. Server access does not automatically supply database credentials. Try the supported Use database login path with a dedicated database account.
No matching data
Inspect the resolved inputs, time range and query result. Confirm that the selected ID exists in the source being queried. For replica reads, account for lag. An empty successful result should not be presented as a connection failure.
For a scatter chart, both selected axes need finite numeric values. Invalid pairs are omitted and reported; missing values are not converted into zero.
The query times out or is truncated
Inspect the plan and actual measurements in Query cost. A result-row cap does not limit scanned rows or aggregation work. Narrow the query and use appropriate source indexes before increasing budgets.
Truncation means the returned batch is incomplete. Do not compute a population-wide decision from that batch unless the query already performed the required aggregation.
A workflow does not run
Confirm that it is published, the reference pins the intended revision, and the actor has current Run/dependency access. Check required input types and the condition branch. A data-condition trigger matches when its query returns records; COUNT(*) = 0 still produces one row unless the query filters it out.
Inspect run/delivery history before retrying an uncertain effect. Use the same request key only for the same intent.
Local development shows different items
Check the selected profile, workspace and project. bun dev, bun dev:local-saas and bun dev:saas can use different storage and identities. Do not delete or recreate a store to recover a missing sidebar item.
Embedded PGlite permits one owning process. Use the existing API for concurrent clients, or PostgreSQL metadata when API and worker run separately. CLI and SDK explains local host ownership.