Errors
Questi contenuti non sono ancora disponibili nella tua lingua.
Errors
Section titled “Errors”Summary
Section titled “Summary”Rokks errors are most useful when read with the current environment, tenant, resource, and job context.
Fields / Parameters
Section titled “Fields / Parameters”| Category | Type | Description |
|---|---|---|
| Authentication | Access | The user must sign in again or lacks permission. |
| Scope | Access | The selected environment or tenant is missing or wrong. |
| Source | Data | The external provider, file, or stream returned unexpected data. |
| Transform | Data | Raw values did not match the configured mapping or type. |
| Query | Dashboard | A widget query could not run or returned invalid columns. |
| Job | Background | A long-running operation failed in one of its steps. |
| Service | Operations | A platform service or dependency is unavailable. |
For SQL Query Stream v1, use the stable code instead of matching message text.
Before response streaming, HTTP 400/405/406/413/415/417 identify
request-contract failures; 503 means execution or lifecycle capacity is
unavailable, and 504 means the initial-header or bounded database phase
deadline expired. After streaming starts, the final terminal.error carries
the bounded code, message, optional position, and retryability signal. A
missing/invalid terminal is a protocol failure and provisional rows are
discarded.
Example
Section titled “Example”If a Web API sync fails, open the stream, then the related job, then the monitoring page if the error points to a service.