Created date: 28.10.2024

Updated by: Emma Camacho

How to use the Has Timeout and TIMEOUT settings?

When creating a Task, it is important to set up a Timeout, especially important if the edition of M&D is Standard, which means that M&D has only 1 execution engine. If this execution engine is busy, other tasks cannot start and will be placed in the queue. The tasks in the queue will start when there's a free execution engine.

Add a timeout to the tasks to ensure that the execution engines are not stuck unnecessarily. For example, if during development the task needs 10 minutes to run, set the timeout to 20 minutes. If the task takes more than 20 minutes, it would mean that something is not working that is outside of M&D's control and the task will be terminated setting the execution engine free to process oder Tasks.

Attention: If the execution engine(s) is(are) busy and they are stuck unnecessarily, it is possible that tasks that should run later will be skipped.

How to use the setting MAXIMUM DELAY?

The Maximum Delay is the time that the Task will be kept on the queue. This setting is especially important if the M&D edition in Standard and has only 1 execution engine. 

Set the Maximum Delay to the time the Task can remain in the queue and it still makes sense to send the report. For example, if a Task should distribute the Morning-Report at 9:00am, the Maximum Delay could be 3 hours as the Morning-Report should not be distributed at 12:00pm. If the execution engines were busy/stuck with other Tasks, the Morning-Report still have the chance to be sent before 12:00pm.

Attention: If the execution engine(s) is(are) busy and the Tasks that should run later have a short Maximum Delay, they will skipped. 

Attention: the default Maximum Delay is 5 minutes (which could be too short).