> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/workflows/push/manage-push.md).

# Manage Push

You can manage your Push from the Settings screen. To go the the push management screen you can click on **Settings** and then click on **Push History.**

<figure><img src="https://34758050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MC1g4I2_CgXd0qAq1P7%2Fuploads%2FrUAm9W3mfP3go68yTMkG%2Fimage.png?alt=media&amp;token=54a7c7ed-8efe-4dd8-b84f-09e018148e77" alt=""><figcaption><p><strong>Push history</strong></p></figcaption></figure>

From this screen you can list all set up push in your org. Quickly identify which report has a push setup. And view a list of Push execution.

### Push Execution

A push execution has a status, a creation and a duration. The status can be either in

**Succes** - Everything went well

**Running** - The push is currently running

**Error** - Their has been an error in the configuration of your push

**Failed** - An internal Whaly error happened and we will retry next period

For a single push execution, we give you access to the logs for 30 days after the execution.


---

# 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.whaly.io/workflows/push/manage-push.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.
