> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-shopify/shopify-reference/orders/order-download/buffertimes.md). # thruDateBuffer and bufferTime ## thruDateBuffer Shopify processes an order after it has been placed to check for invalid or fraudulent activity. This process typically takes 5 minutes. If HotWax Commerce syncs the order before Shopify finishes processing it, HotWax Commerce will need to search for the order in Shopify again to update its tags. The thruDateBuffer delays order syncing from Shopify for a specific amount of time. This delay gives Shopify time to process and analyze orders before HotWax Commerce imports them, which reduces the need to recheck order tags. By default, this value is 5 minutes. ## bufferTime Orders can be missed if they are placed during the microsecond time gap between two consecutive jobs. To address this, HotWax Commerce adds a buffer time padding to the start time of each job. This creates an overlap between jobs and prevents orders from being lost during these microsecond gaps. The bufferTime is calculated based on the previous job's run time and includes both the thruDateBuffer and the overlap time. By default, the bufferTime is 6 minutes (5 minutes for thruDateBuffer and 1 minute for overlap). ## Example scenario * Sync job interval: Every 15 minutes * Default values: `thruDateBuffer` = 5 minutes, `bufferTime` = 6 minutes 1. The job running at 1:15 syncs orders from 12:54 to 1:10. 2. The job running at 1:30 syncs orders from 1:09 to 1:25. This overlap processes orders accurately and reduces the risk of discrepancies. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.hotwax.co/documents/learn-shopify/shopify-reference/orders/order-download/buffertimes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.