| Symptom | First check |
|---|---|
| Workspace appears empty | Confirm the application address, account, and selected workspace. |
| Cannot edit | Check your role, workbook archive state, and the specific rule error. |
| Proposal will not apply | Refresh a stale revision and review again; do not repeatedly replay the old preview. |
| AI remains queued | Ask the operator to check the background worker and database connection. |
| AI is unavailable | Keep your draft, retry later, edit manually, or explicitly choose the limited built-in helper. |
| A chart is blank | Inspect its source, filters, mapped fields, and repair message. |
| An invitation is rejected | Use the invited verified email address; check expiry or request a replacement link. |
| Email is not visible to a teammate | The owner must intentionally share the linked conversation. |
| A form will not submit | Refresh changed forms and inspect required fields, current options, and sheet rules. |
| A PDF will not finalize | Resolve missing mapped values and invalid relationship/field bindings. |
| Agent is waiting | Check its next scheduled check, daily allowance, missing evidence, source grants, supervisor, and pending reviews. Waiting is not automatically a failure. |
| App participant cannot continue | Check publication, current invitation or group access, assigned record scope, task revision, and per-app pause. |
| Integration is unavailable | Integration private-preview admission is separate from general Ralti access. A catalog listing does not establish account availability. |
| An external action may already have happened | Inspect the provider and reconcile the existing run before retrying. Do not create a second action to test the first. |
Preserve useful work#
Keep a draft when the problem is a temporary provider or network failure. For a revision conflict, compare the latest record before reapplying your intended change. The iPhone and iPad app follows the same save, review, and permission checks as the website. Never assume a timeout means a server job stopped.
Send a useful support report#
- Include the feature and page, visible error, time and timezone, and device/browser.
- Describe the smallest steps that reproduce the problem and what you expected to happen.
- Say whether the problem affects one record, one workspace, one account, or every device.
- Include a redacted screenshot when layout or text matters. Keep passwords, tokens, provider keys, invitation capabilities, and private environment files out of the report.