Execute the same job multiple times at the same #79
Replies: 1 comment 2 replies
-
To me, it makes more sense to treat identical schedules and jobs as a single registry entry. The system should log a visible warning indicating that only the first schedule entry will be used, along with a detailed reason why this decision was made. Only if the name, parameters, etc., are different should each have its own entry. My reasoning is that if concurrency is not set and you have a job type with multiple identical schedules, you end up with multiple objects that are essentially the same and can only run one at a time. In this instance, the system will oscillate between each registry entry even though the job is exactly the same. This can lead to inefficient resource utilization and potential confusion. That said, this behavior could be controlled by a configuration setting with a sensible default. Once we finalize the configuration, this could be categorized as an |
Beta Was this translation helpful? Give feedback.
-
Given a job registration as the following:
This seems like a valid case - I want to have a job that gets triggered every hour two times but with a different set of parameters.
If we generalize from here, should this be valid?
That said: The sample given above: Should this be one or two executions at the same time?
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions