> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2023.4-changes-overview/enhancement-highlight-expiring-schedules.md).

# Enhancement: Highlight Expiring Schedules

## Overview

To help with easier management of Schedule information in Builder, we've added further filters which highlight which data is expiring soon or already has done, to help you better manage which schedules records you need to upload more data on to keep their related processes running as desired.

Now, when you go to the schedules screen you'll see the number of schedules that have expired at the top.

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FLvlOQzJYHlyOoFgQ7QqF%2Fimage.png?alt=media&amp;token=70db0e53-f3c0-4b5b-ada7-531d374dda62" alt=""><figcaption></figcaption></figure>

You can also use the new filter function to see schedules that have already expired or are about to expire in certain time frames. The options are:

* Already expired
* Expiring within next 7 days
* Expiring within next 30 days
* Expiring within next 90 days
* Select Date - here you can choose a custom date.

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FfysDQpM8WBNsvyLvJbYi%2Fimage.png?alt=media&amp;token=2606504d-85ed-40af-9735-e51a92342c2d" alt=""><figcaption></figcaption></figure>


---

# 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.enate.net/whats-new/older-versions/changes-overview-older-versions/2023.4-changes-overview/enhancement-highlight-expiring-schedules.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.
