# query_timeout

> The request took too long to compute. What causes the BioFlow API's query_timeout error (HTTP 503) and how to fix it.

Page: https://getbioflow.com/docs/api/errors/query-timeout

{/* Generated by apps/docs/scripts/generate-api-surface.mjs from openapi/v1.json — do not edit by hand. */}

HTTP 503 · `application/problem+json` · The request took too long to compute.

## What causes it [#what-causes-it]

* The database cancelled the read because it ran too long — today that is `GET /v1/analytics/summary` with `range_days=90` on a workspace with a lot of traffic. Nothing was changed.

## How to fix it [#how-to-fix-it]

* Wait the number of seconds in the `Retry-After` header and retry, or ask for a shorter range (`range_days=30` or `7`).
* If `range_days=30` fails too, contact [support@getbioflow.com](mailto:support@getbioflow.com) and quote the `request_id`.

## Example response body [#example-response-body]

```json
{
  "type": "https://getbioflow.com/docs/api/errors/query-timeout",
  "title": "The request took too long to compute",
  "status": 503,
  "instance": "urn:request:req_01abc",
  "code": "query_timeout",
  "request_id": "req_01abc"
}
```

Branch on the stable `code` field — `title` and `detail` are for humans and may
change. `type` (`https://getbioflow.com/docs/api/errors/query-timeout`) always resolves to this page. Quote
`request_id` when contacting support. Full code registry on the
[API docs hub](https://getbioflow.com/docs/api#errors); the complete surface is in the
[interactive reference](https://getbioflow.com/docs/api-reference).
