> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/navigation/reload.md).

# Reload

Reload is the action that instructs the browser to refresh and reload all content of the current webpage, similar to pressing the circular arrow button (F5) on the browser. This action operates automatically and does not have any accompanying configuration parameters.

🎥 Watch the tutorial video: [Here](https://youtu.be/a9qNt96X1SM).

#### Practical example: Troubleshooting when the webpage is faulty or temporarily disconnected

During the automation process, you may sometimes encounter situations where the webpage displays errors, popup dialogs freeze and cannot be closed, or network congestion causes some elements on the interface to fail to load.

* How to apply: Combine the If conditional block with the Wait element or Image exists action. If the target element is not found after a certain period (the webpage is faulty), you let the script call the Reload action.
* Result: The browser will reload the page data from the beginning to fix temporary display errors, allowing the script to self-recover from errors and continue operating without abruptly stopping the flow.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gpmautomate.com/automate-en/action-guide/navigation/reload.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
