504 application/problem+json
application/problem+json. Branch on type (a stable URI), not on title
or detail (human-readable, may change).
When it occurs
The query was too broad to finish inside the server-side statement-timeout cap. This protects the shared connection pool — it is the cap working, not an outage.How to fix
Narrow the filters (jurisdiction, date range, target_segment, bbox) and retry. A narrower query returns well within the timeout.
Retryable — retry with exponential backoff (respect Retry-After on 429/503).
See the full error catalog for the response shape and retry matrix.
Every response carries an x-request-id header — include it in any support request.