> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/data-api-sdk/api-endpoints-errors-and-migrations/garmin-async-processing-and-cache.md).

# Why does the API return "Request is processing" instead of data?

For some providers (notably Garmin), the first REST request for a given period returns **`Request is processing, try again later`** while the data is fetched asynchronously. This is a processing event with no `data` field, not an error.

{% stepper %}
{% step %}
Wait the seconds given in `retry_after_seconds`.
{% endstep %}

{% step %}
Repeat the identical request. It is then served from cache instantly.
{% endstep %}
{% endstepper %}

Handle incoming payloads by their `type` field and ignore or log non-data event types rather than failing your decoder.

Separately, **Garmin sends data once and expects you to store it.** Terra does not retain provider data indefinitely, so persist data on first receipt; re-requesting older ranges may fail (for example a `500`). To re-trigger a historical pull, you can deauthenticate and reauthenticate the user for a fresh backfill within the provider's limits. See [requesting historical data](https://docs.tryterra.co/health-and-fitness-api/managing-user-health-data/requesting-historical-data).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/data-api-sdk/api-endpoints-errors-and-migrations/garmin-async-processing-and-cache.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.