ChengLong GU 35d33bea75
fix(frontend): treat invalid cron fields as non-scheduled (#8020)
* fix(frontend): keep invalid cron schedules as custom

* test(frontend): cover inclusive cron bounds

* docs(scheduled-tasks): note cron preset bounds

The form keeps an out-of-range cron as custom; the guide now says which
numeric ranges a preset covers and that saving such an expression returns
422. CHANGELOG entries cover the fix.

* docs(scheduler): clarify invalid cron save validation

---------

Co-authored-by: Nan Gao <thunderggnn@gmail.com>
2026-11-14 16:36:25 +08:00
..