Broker tasks in 'Failed' status are automatically rescheduled

It may happen that a broker task cannot be executed successfully, for example because services are temporarily unavailable or because a swap file is in use. These tasks - which end up in status 4 'Failed', because the maximum execution time has been exceeded - will now be automatically rescheduled. You can specify the maximum number of incorrect executions per broker task. If this value is exceeded, the task will still end up in status 4.