PrefectHQ
Artificial Concurrency Delay for the Map Function
Describe the current behavior
The current map functionality is very useful for triggering the same task with different input values simultaneously. However, when we utilize the map function, all tasks start executing at the same time without any delay between them. This concurrent execution can create conflicts during the run, leading to issues such as resource contention or race conditions.
Describe the proposed behavior
To enhance the reliability and efficiency of the map function, it would be beneficial to implement a feature that allows users to control the execution delay between tasks which is running from map. By doing so, we can mitigate conflicts during task runs and ensure a smoother workflow overall.
Example Use
No response
Additional context
No response
hi @majo-aqfer - thank you for the issue!
would you be able to fill out the Example Use section so we can get an idea of what DX you're interested in?
