render-timeout
| Status | 504 |
| Title | Render timed out |
| Code | render-timeout |
| Type | https://docs.satellitedata.net/problems/render-timeout |
Available now Lean v1 can return this problem.
Meaning
Section titled “Meaning”A render ran past the synchronous time limit of 29 seconds.
Likely causes
Section titled “Likely causes”- A tile over a long time window that touches many scenes.
- A large process output close to the size cap.
- In lean v1 this answer comes from the gateway, so the request id is in
requestIdonly.
Narrow the time window, zoom in, or lower the output size. For process, send the request as a job to POST /v1/process/jobs.
Example
Section titled “Example”The detail is the example from the v1 contract.
{ "type": "https://docs.satellitedata.net/problems/render-timeout", "title": "Render timed out", "status": 504, "detail": "The render read 41 scenes and did not finish in 29 seconds. Narrow the time range or lower the output size.", "instance": "/v1/...", "code": "render-timeout", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}See Errors for the members every problem carries.