# Create a cut-off

There are two panels in the **Dataflow Modeler** page where cut-offs can be created:

* **Dataflow Properties** → **Dataflow cut-off**: this panel appears when a dataflow is designed in the Dataflow Modeler pane.
* **Node Properties** → **Node Cut-off list**: this panel appears when a node is selected in the Dataflow Modeler pane.

You can refer to the [Dataflow Properties panel](/data-watcher-1.21/model/dataflow-properties-panel.md) and [Node Properties panel](/data-watcher-1.21/model/node-properties-panel.md) pages for details.

Follow these steps to create a cut-off in the **Dataflow cut-off** panel:

{% hint style="info" %}
The cut-off creation process is the same both in the dataflow cut-off panel described below and in the node cut-off list panel!
{% endhint %}

1. In the **Dataflow Properties** panel, click on the **NEW** button.
2. In the **New Dataflow cut-off** panel, the **Enable** toggle is on by default. Click on it if you want to disable the cut-off.
3. Enter a **Name** for your cut-off.
4. Choose the **Category**: **Duration** or **Planned** according to your needs - see the sections below.
5. Click the **SAVE** button. Once you have saved a cut-off, it will appear in the dataflow cut-off list below. Click on the 3-dots icon to **Disable**, **Edit,** or **Delete** the cut-off.

{% hint style="warning" %}
You can only add one duration cut-off per flow!
{% endhint %}

## **Duration type cut-off**

* **Max duration time**: enter minutes of the time interval as needed.
* **Activity Type** (only for node cut-offs):
  * Any: any event occurring in the system, e.g. the anti-virus scan, an incoming event, an outgoing event.
  * Incoming: the timer will stop when the file enters the flow.
  * Outgoing: the timer will stop when the file exits the flow.
* **Warning**:
  * No (default).
  * Select how many minutes before an event the warning will be sent. Values go from 1 minute to 360 minutes (6 hours).
* **Notification**: configure notifications for your cut-offs. Learn more [here](/data-watcher-1.21/model/notifications.md).

## **Planned type cut-off**

* **Activity Type** (only for node cut-offs):
  * **Any**: any event occurring in the system, e.g. the anti-virus scan, an incoming event, an outgoing event.
  * **Incoming**: the timer will stop when the file enters the flow.
  * **Outgoing**: the timer will stop when the file exits the flow.

### **Time settings panel**

* **Calendar**:
  * Every day
  * Every working day
  * Administrators can configure additional calendars, see [Cut-off calendars](/data-watcher-1.21/setup/cut-off-calendars.md).
* **Time zone**: select the time zone.
* **Time**: set at what time the file must have reached the required status.
* **Cron**: either set a cron expression manually or click on the **Generate** button.
* **Max advance**: it can be modified as described in **Define a time window for early cut-offs** here below.
* **Cut-Off evaluation delay**: when the checkbox is selected, Data Watcher is granted additional time **after** the cut-off time to evaluate whether a file arrived on time. The **expected delivery time remains unchanged**.\
  The minutes shown by default in the cut-off evaluation delay field are set in the [Advanced Settings](/data-watcher-1.21/setup/advanced-settings/cut-off-evaluation-delay.md). \
  Example:\
  \- A file is expected by 7:55 a.m.\
  \- A 5-minute **Cut-off evaluation delay** is configured.\
  \- Data Watcher will update the cut-off board at 8:00 a.m.\
     \- If the file arrived by 7:55 a.m., it is considered on time.

     \- If it arrived after 7:56 a.m., it is considered late.\
  This feature is especially useful for organizations with high file volumes, helping to reduce **cut-off false alarms** caused by minor processing delays.
* **Warning**:\
  \- No (default).\
  \- Select how many minutes before an event the warning will be sent. Values go from 1 minute to 360 minutes (6 hours).

### **Instances panel**

{% hint style="warning" %}
The Instances panel is a Dataflow Cut-off option only!
{% endhint %}

* **Instances configuration**:
  * **Single Instance Dataflow**: select this option when one dataflow instance is expected for the time range.
  * **Multiple Instance Dataflow**: in the **Number of Instances** field, enter the number of expected Dataflow instances for each time range set.
  * **Ignore exceeding completed instances**: this option is enabled by default, and the cut-off status is not affected by several completed instances higher than expected. When the option is disabled, if at least one exceeding instance is completed, the cut-off evaluation status will turn into "Error" and instances will be marked as "Overflow".

### **Notifications panel**

* **Notifications**: configure notifications for your cut-offs. Learn more [here](/data-watcher-1.21/model/notifications.md).


---

# 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/create-a-cut-off.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.