Error Codes
Soln shows errors in a compact format so that you can quickly decide what to do next and share useful information with an administrator or support team.
Most full-page errors show a large status code, such as 404 or 503, and a short status text, such as Not Found or Service Unavailable.
When you inspect a failed request, you may also see three structured fields:
| Field | What it means |
|---|---|
code | The stable error category. It describes the general type of failure |
reason | The specific reason for this failure. It is short and readable, for example provider_timeout |
domain | The product area where the failure happened, for example assistant, form_data, iam, or workspace_app |
You do not need to memorize these fields. They are mainly there to help administrators locate the right system area.
What You See on the Page
If a page cannot load, Soln shows the HTTP status code for that page:
| Status | Meaning | What you can try |
|---|---|---|
400 Bad Request | The request was not valid | Refresh the page. If it repeats, check whether the link or selected item is still valid |
401 Unauthorized | You are not signed in or your session expired | Sign in again |
403 Forbidden | Your account does not have access | Ask an administrator to check your role or permission |
404 Not Found | The item or page no longer exists | Go back to the list and open the item again |
408 Request Timeout | The request took too long | Retry after a short wait |
409 Conflict | The action conflicts with the current state | Refresh and check whether someone else changed the item |
422 Unprocessable Entity | The system understood the request, but some data cannot be processed | Review the data you submitted |
429 Too Many Requests | Too many requests were sent in a short time | Wait and retry |
499 Client Closed Request | The browser or client closed the request before it completed | Retry if you still need the result |
500 Internal Server Error | The service failed unexpectedly | Retry once. If it repeats, contact an administrator |
502 Bad Gateway | A dependent service returned an invalid response | Retry later |
503 Service Unavailable | A service is unavailable or temporarily overloaded | Retry later or ask an administrator to check service status |
504 Gateway Timeout | A dependent service did not respond in time | Retry later |
Common Reasons
The reason value helps narrow down the cause:
| Reason | Usually means |
|---|---|
provider_timeout | The AI provider request or Assistant tool chain timed out or was aborted |
provider_request_failed | The AI provider request failed before Soln received a successful response |
content_filtered | The request or response was blocked by provider safety rules |
model_not_found | The selected AI model is not available |
record_not_found | A form record no longer exists or cannot be accessed |
permission_denied | The current user or integration does not have permission |
record_ids_required | The action requires one or more record IDs |
The same reason can appear in different areas. The domain tells you where it happened.
What to Send to an Administrator
When reporting an error, include:
- the page or action you were using
- the large status code shown on the page
- the approximate time of the failure
- whether you refreshed, changed page, cancelled, or started another run
For Assistant errors, also include the selected model and whether the response had already started streaming.
When to Retry
Retry is usually safe for:
408,429,499,502,503, and504provider_timeoutprovider_request_failedwhen no data was saved
Do not keep retrying immediately if the same error repeats. Wait briefly or ask an administrator to check service status, permissions, or provider configuration.