> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-user-manual/common_elements/time-range-selection.md).

# Time range selection

View date and time range.

Use the time range selector to control what period is shown in graphs and lists.

Click the time range button in the upper-right corner of the **Overview** section.

The button label reflects the current selection.

Default is **Last 7 days**.

The selection applies to all views.

<figure><img src="https://content.gitbook.com/content/EANwXRnuP0ug8971viyg/blobs/9RuXhOFBX3jzeqjBuOWU/image.png" alt=""><figcaption></figcaption></figure>

### Preset ranges

Select one of these ranges:

* **Last 24 hours**
* **Last 3 days**
* **Last 7 days**
* **Last 30 days**
* **Custom Range**

### Custom Range

If you select **Custom Range**, a form opens.

Select the start and end date.

To set exact times, use the start and end time fields below the calendar.

<figure><img src="https://content.gitbook.com/content/EANwXRnuP0ug8971viyg/blobs/s3q26JsSMleZ8UcXBHCA/image.png" alt=""><figcaption></figcaption></figure>

Click **Apply**.


---

# 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://help.boomerang3.com/boomerang-3-user-manual/common_elements/time-range-selection.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.
