Currently, the Scheduler Agent supports only 5-part cron expressions (minute, hour, day, month, day-of-week), which limits the scheduling precision to a minimum of one-minute intervals.
To support use cases that require higher precision (e.g., execution every 10 or 30 seconds), the agent should optionally support 6-part cron expressions with a seconds field.
Proposed Enhancement:
-
Add support for 6-part cron format: seconds minutes hours day month day-of-week.
-
Introduce a new configuration option:
- Use Seconds (boolean) or Six-Part Format (enum/flag).
-
When enabled, the agent interprets the first field as seconds.
-
When disabled (default), the agent continues to use the standard 5-part format for backward compatibility.
Example:
*/10 * * * * * → every 10 seconds (with "Use Seconds" enabled)
*/1 * * * * → every 1 minute (default behavior)
Backward Compatibility:
- The existing behavior remains unchanged unless the new option is explicitly enabled.
- Validation logic should distinguish between 5-part and 6-part formats based on the setting.
Currently, the Scheduler Agent supports only 5-part cron expressions (minute, hour, day, month, day-of-week), which limits the scheduling precision to a minimum of one-minute intervals.
To support use cases that require higher precision (e.g., execution every 10 or 30 seconds), the agent should optionally support 6-part cron expressions with a seconds field.
Proposed Enhancement:
Add support for 6-part cron format:
seconds minutes hours day month day-of-week.Introduce a new configuration option:
When enabled, the agent interprets the first field as seconds.
When disabled (default), the agent continues to use the standard 5-part format for backward compatibility.
Example:
*/10 * * * * *→ every 10 seconds (with "Use Seconds" enabled)*/1 * * * *→ every 1 minute (default behavior)Backward Compatibility: