# Define a time window for early Cut-offs

If a cut-off notice arrives hours after the expected time, an optimist will see it as an early notice and a pessimist as a late notice. Both of them may be right. To solve this ambiguity, the **Max Advance** field can be used to define a time window within which an early cut-off is accepted. Isn't this smart?

For example, imagine that a daily cut-off is defined every day at **noon**. If a file arrives at **8 am**, it might be a file exceeding the cut-off of the day before (therefore late) or a file arriving earlier than expected (therefore in advance). The **Max Advance** field solves this ambiguity. In our example, setting the Max Advance field to 6 hours, the file arriving at 8 am would be in advance and therefore correct.

This field is updated automatically according to the value entered in the **Time** field. However, it can be modified as needed, selecting from 1 to 24 hours.

When a cut-off is set on the node, the clock symbol appears in the node box.


---

# Agent Instructions: 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://docs.primeur.com/data-watcher-1.21/model/cut-offs/define-a-time-window-for-early-cut-offs.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.