Troubleshooting
Most problems fall into two groups: something failed while the runtime was deployed, or the workspace shows an error while you work on data. Start from the symptom, then open the matching page.
| Symptom | Page |
|---|---|
A CLI command failed, or the runtime never becomes ready | Deployment Troubleshooting |
A page shows a status code such as 400, 403, 500, or 503 | Error Codes |
| A form, record, or button is missing for one member | Roles & Permissions — entry and resource permissions decide what the member sees |
| An approval process did not run as expected | Approval Process Execution Logs |
| An automation task did not run as expected | Automation Task Execution History |
| An OpenLink flow did not run as expected | Flow Logs |
What To Collect Before Asking For Help
These details make the cause much faster to find:
- the address of the page and the action you were performing
- the status code, plus the
code,reason, anddomainvalues shown on the page or in the failed request - for an approval process, automation task, or OpenLink flow, the execution record and the error it recorded
- for a deployment problem, the output of
soln statusandsoln doctorrun in the deployment directory
Related
- Error Codes explains the status codes and the structured error fields
- Deployment Troubleshooting covers CLI and runtime startup problems
- Overview shows where the rest of the documentation starts