-
Suggestion
-
Resolution: Duplicate
Problem Definition
Currently, there's no way to produce an even load on the system when running multiple scheduled automation rules; this can cause performance issues in instances with heavy use of scheduled automation rules, with large spikes on common scheduled times (e.g. 9 a.m.). This also creates a challenge to scale operations effectively.
Suggested Solution
Add a CRON expression that produces an even load on the system, running in an "interval"; for example, instead of running all automations precisely at 9 a.m., they would have an interval, 9 a.m. to 10 a.m., and would run evenly between this period, avoiding performance impacts.
Here are a couple of examples using the letter "H" as the expression:
- 0 0 H(9-10) ? * MON-FRI
It would run every Monday, Tuesday, Wednesday, Thursday, and Friday between 9 a.m. and 10 a.m.
- 0 0 H 15 * ?
It would run any hour on the 15th day of every month.
- duplicates
-
AUTO-159 Improve Automation concurrency - request for expanding resources in automation, give visibility of how many number of concurrent executions are available in Automation, support monitoring of Automation queue
- Gathering Interest