--- title: How to set max duration on stops description: You can set a max duration on a stop, this is useful for when one has a stop that always happen in a process, which can't be avoided. For example, say that in a startup process for a new product, you --- [Skip to content](https://kb.dataintel.dk/how-to-set-max-duration#main-content) English Show submenu for translations [Submit a request](https://kb.dataintel.dk/kb-tickets/new?hsLang=en) ![DIAP-1.png\]](https://kb.dataintel.dk/hs-fs/hubfs/DIAP-1.png?height=41&name=DIAP-1.png) - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) Open main navigation Close main navigation - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) - English Show submenu for translations - [Submit a request](https://kb.dataintel.dk/kb-tickets/new) - Go to Data Intelligence A/S Go to Data Intelligence A/S Hello. How can we help you? - There are no suggestions because the search field is empty. 1. [Help Center](https://kb.dataintel.dk/?hsLang=en) 2. [OEE site](https://kb.dataintel.dk/oee-site?hsLang=en) 3. [Guides](https://kb.dataintel.dk/oee-site?hsLang=en#guides) # How to set max duration on stops ### Introduction - This guide describes how you can set a max duration on a stop, when it is categorized to a stop cause. ### Max duration You can set a max duration on a stop, this is useful for when one has a stop that always happen in a process, which can't be avoided. For example, say that in a startup process for a new product, you have a stop that always happens and it last 2 minutes. When you can use this function to ensure that the stop created from this process max can last 2 minutes in the OEE, if when that the stop last longer than 2 minutes, a new stop will be created, which can be categorized just like any other stop. ### Set max duration on a stop cause To set a **max duration** on a stop cause go to **Configuration -\> Stop causes**: ![](https://kb.dataintel.dk/hubfs/image-png-Jul-02-2021-06-52-26-21-AM.png) Find the stop cause and click the **edit** button: ![](https://kb.dataintel.dk/hubfs/image-png-Mar-30-2022-08-16-04-81-AM.png) Set **Max duration (sec.)** to the duration the stop cause may maximum last in seconds. **Max duration** is enabled on the **stop cause** when **Max duration (sec.)**  \> 0: ![](https://kb.dataintel.dk/hs-fs/hubfs/image-png-Mar-30-2022-08-18-08-78-AM.png?width=566&name=image-png-Mar-30-2022-08-18-08-78-AM.png) Click **Apply**: ![](https://kb.dataintel.dk/hs-fs/hubfs/image-png-Mar-30-2022-07-57-40-91-AM.png?width=197&name=image-png-Mar-30-2022-07-57-40-91-AM.png) This can also be done, when you create a new **stop cause**. ### How to use max duration in Production status **Max duration** is used, when a stop is categorized to a stop cause with a **max duration**. In **Views -\> Production status**: ![](https://kb.dataintel.dk/hubfs/image-png-Jul-02-2021-06-57-07-76-AM.png) Click **Stop causes** (If it is grayed out, that means that there are no stops, that needs to be categorized): ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360009667199mceclip1.png) Select a stop to **Categorize**: ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-01-05-55-42-PM.png) A stop cause using **Max duration** will have this opposite arrows icon: ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-10-20-53-14-AM.png) Select a stop cause that has this icon:![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-01-48-47-91-PM.png) In our example **Max duration(sec.)** is set to 120 seconds -\> 2 minutes and the stop lasted 2 minutes and 7 seconds. The stop is split and an new with the remain duration after the 2 minutes is created and ready to be categorized:  ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-01-53-03-19-PM.png) The new stop's stop cause is the original stop cause. Here is a little diagram of what happened with the stop: ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-02-00-30-30-PM.png) ### Set stop cause after max duration on a stop cause You can setup which stop cause the new stop will have. To do this click the **edit** on the stop cause again: ![](https://kb.dataintel.dk/hubfs/image-png-Mar-30-2022-08-16-04-81-AM.png) And set a stop cause for **Stop cause after max. duration**, click **Change**: ![](https://kb.dataintel.dk/hs-fs/hubfs/image-png-Mar-30-2022-08-19-27-00-AM.png?width=536&name=image-png-Mar-30-2022-08-19-27-00-AM.png) Select a stop cause: ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-02-15-17-57-PM.png) and click **Change**: ![](https://kb.dataintel.dk/hs-fs/hubfs/image-png-Dec-08-2021-02-16-11-04-PM.png?width=367&name=image-png-Dec-08-2021-02-16-11-04-PM.png) Click **Update**: ![](https://kb.dataintel.dk/hubfs/image-png-Mar-30-2022-08-01-15-06-AM.png) Now when you categorize a stop to to the stop cause: ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-01-05-55-42-PM.png) ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-01-48-47-91-PM.png) The new stop will have the stop cause set in **Stop cause after max. duration**: ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-02-14-40-70-PM.png) And this is what happened to the stop: ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-02-19-19-28-PM.png) With **Stop cause after max. duration** set, the new stop will have the stop cause tree under the new stop cause, instead of the original stop cause, this can be used to ensure, that the new stop can't be categorized to the same stop cause the original stop was: ![](https://kb.dataintel.dk/hubfs/image-png-Dec-08-2021-02-28-46-33-PM.png) - [DIAP Gateway](https://kb.dataintel.dk/diap-gateway?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/diap-gateway?hsLang=en#getting-started) - [Troubleshooting](https://kb.dataintel.dk/diap-gateway?hsLang=en#troubleshooting) - [Known issues/limitations](https://kb.dataintel.dk/diap-gateway?hsLang=en#known-issues-limitations) - [General](https://kb.dataintel.dk/general?hsLang=en#main-content) - [FAQ](https://kb.dataintel.dk/general?hsLang=en#faq) - [Configuration](https://kb.dataintel.dk/configuration?hsLang=en#main-content) - [FAQ](https://kb.dataintel.dk/configuration?hsLang=en#faq) - [Troubleshooting](https://kb.dataintel.dk/configuration?hsLang=en#troubleshooting) - [Guides](https://kb.dataintel.dk/configuration?hsLang=en#guides) - [Protocols](https://kb.dataintel.dk/configuration?hsLang=en#protocols) - [Live/Real time site](https://kb.dataintel.dk/live-real-time-site?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/live-real-time-site?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/live-real-time-site?hsLang=en#faq) - [Guide](https://kb.dataintel.dk/live-real-time-site?hsLang=en#guide) - [Features](https://kb.dataintel.dk/live-real-time-site?hsLang=en#features) - [OEE site](https://kb.dataintel.dk/oee-site?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/oee-site?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/oee-site?hsLang=en#faq) - [Guides](https://kb.dataintel.dk/oee-site?hsLang=en#guides) - [Configuration](https://kb.dataintel.dk/oee-site?hsLang=en#configuration) - [Remote Access](https://kb.dataintel.dk/remote-access?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/remote-access?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/remote-access?hsLang=en#faq) - [Guides](https://kb.dataintel.dk/remote-access?hsLang=en#guides) - [API](https://kb.dataintel.dk/api?hsLang=en#main-content) - [API](https://kb.dataintel.dk/api?hsLang=en#api) - [Release information](https://kb.dataintel.dk/release-information?hsLang=en#main-content) - [DIAP Release Notes](https://kb.dataintel.dk/release-information?hsLang=en#diap-release-notes) - [Live/Real time site](https://kb.dataintel.dk/release-information?hsLang=en#live-real-time-site) - [OEE site](https://kb.dataintel.dk/release-information?hsLang=en#oee-site) - [Management site](https://kb.dataintel.dk/release-information?hsLang=en#management-site) - [DIAP Gateway](https://kb.dataintel.dk/release-information?hsLang=en#diap-gateway) - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) [![Chill listening crop-3](https://kb.dataintel.dk/hs-fs/hubfs/Sk%C3%A6rmbillede%202021-05-04%20kl.%2017.46.04.png?width=221&height=26&name=Sk%C3%A6rmbillede%202021-05-04%20kl.%2017.46.04.png "Chill listening crop-3")](https://diap.hubspotpagebuilder.com/-temporary-slug-5b226bcb-69c8-45c1-82ff-e060e2d4037d?hsLang=en) Copyright © 2026, Data Intelligence A/S