# Troubleshoot a problem

Find the cause and collect useful information without exposing private data.

Audience: Everyone

Reviewed: 2026-11-05

Canonical path: /docs/troubleshooting

## Check context

1. Record app, table and intended action.
2. Confirm signed-in identity, account and workspace.
3. Read the error and check whether the operation nevertheless completed.
4. Use a harmless example only if it will not duplicate a record, message or payment.

## Cannot create or see data

For creation, check creator seats, subscription/trial, app slots and separate AI allowance. A template failure is not necessarily an AI problem.

For missing records or lookup labels, check shares, row access, filters and target relationships. Missing data can be intentional access control; ask the owner to verify intended access.

## Save or import failed

Check required values, types, subscription, record allowance and approvals. Read partial-import results before retrying. If another user changed a record, refresh and reconcile rather than overwrite blindly.

## Automation or delivery failed

Check saved rule, event and conditions, then available Workflow Logs and the destination separately. For forms, inspect response and List-delivery status in the editor. Investigate uncertain sends before repeating them.

## Useful support details

- Expected and actual result.
- Time and time zone, app/table name and exact error.
- Reproduction steps with non-sensitive values.
- A screenshot of the control/error with private records and file links obscured.
- Whether one or several users are affected.

## Keep private information private

Do not share passwords, keys, tokens, card details, customer exports or secret-bearing URLs. An external AI should receive only information you are authorised to share. Use Help for the current support route.

## Related guides

- [Allowances and product boundaries](/docs/limits)
- [Records, imports and exports](/docs/records-and-imports)
- [Create workflows with AI or the editor](/docs/workflows)