Maximum task call exceeded when looping over tasks more flexible

[hans-d]

Currently, there is a hardcoded limit for the maximum task call.

In my use case, I'm using it wilt some nested loops to call a task with very specifc vars per loop. Having a specific task for this is making sense for me as 1) I can use labels to see progress and 2) can implement some status checks to see if the task actually needs to be executed in full.
The initial execution is > 1000, but subsequent ones are in most cases way less when combined with the status check.

1. can we have some parameter/config to specify a different max number
2. can we have this check against eg the label, or the structure that is used for run: when changed ?
3. option not to increase the counter when the task is skipped depending on the status/ changed sources ?

Currently using a workaround by not calling a task on a loop, but invoking a command 'task '

[pd93]

Duplicate of #820. I have posted an update there. Feel free to contribute to the discussion in that issue.