> 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/webhook/payload-content-and-provider-quirks/garmin-payload-simulator-not-stored.md). # Why don't Garmin simulator payloads appear in history? Payloads created via the payload generator/simulator are **not stored**, so they will not appear in payload history even when the response body shows success. A few related points: * The simulator preview can differ slightly from what lands in a storage destination, where the file contains a dump of the entire payload. The underlying data content is the same. * Auth/reauth events can legitimately show paired `200` and `500` statuses. * If real delivery is failing, **check your own destination configuration first** (for example an S3 bucket policy), as that is more often the cause than Terra. --- # 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/webhook/payload-content-and-provider-quirks/garmin-payload-simulator-not-stored.md?ask= ``` 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.