> For the complete documentation index, see [llms.txt](https://search.guides.reactify.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://search.guides.reactify.com.au/troubleshooting-and-faq/how-long-should-it-for-published-changed-to-reflect-on-the-front-end.md).

# How long should it for published changed to reflect on the front end?

It should be no more than **5 minutes** for all customers.

It's based on when the config cache expires which is every five minutes, so if the merchant visits the site at **10:01am** their config will expire at **10:06am** so any changes made between **10:01am** and **10:06am** will appear **after 10:06am**.

Also, if the merchant make the change at **10:03am**, even though they won't see it until **10:06am** other customers may begin seeing it immediately depending on when their 5 minute cache is set to expire.


---

# 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://search.guides.reactify.com.au/troubleshooting-and-faq/how-long-should-it-for-published-changed-to-reflect-on-the-front-end.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.