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
..
2026-10-12 19:00:54 +08:00
2026-11-09 20:42:29 +08:00
2026-11-12 20:30:17 +08:00
2026-11-14 12:22:22 +08:00
2026-11-11 13:26:17 +08:00
2026-04-10 20:24:52 +08:00
2026-09-28 16:02:34 +08:00
2026-10-27 09:46:58 +08:00
2026-10-31 23:00:39 +08:00
2026-07-22 08:42:36 +08:00
2026-09-16 21:19:52 +08:00
2026-08-01 22:19:59 +08:00
2026-11-13 23:01:38 +08:00
2026-11-11 20:59:05 +08:00
2026-11-14 12:22:22 +08:00
2026-07-08 17:10:27 +08:00
2026-09-29 17:23:36 +08:00
2026-10-15 15:10:39 +08:00
2026-09-30 10:14:42 +08:00
2026-11-11 13:26:17 +08:00
2026-11-11 20:59:05 +08:00
2026-11-11 13:26:17 +08:00
2026-10-25 15:13:16 +08:00
2026-11-12 09:09:44 +08:00
2026-11-14 16:36:25 +08:00
2026-11-13 23:01:38 +08:00
2026-11-11 20:59:05 +08:00
2026-11-14 12:22:22 +08:00
2026-07-05 00:12:16 +08:00
2026-11-01 23:24:07 +08:00
2026-09-27 10:57:24 +08:00
2026-11-05 15:10:21 +08:00
2026-10-29 22:26:12 +08:00
2026-07-28 19:35:21 +08:00
2026-11-04 20:16:09 +08:00
2026-11-12 20:30:17 +08:00
2026-01-22 00:26:11 +08:00
2026-02-08 22:43:51 +08:00
2026-09-16 18:46:18 +08:00
2026-11-12 20:30:17 +08:00
2026-11-02 15:29:46 +08:00
2026-11-12 20:30:17 +08:00
2026-10-08 09:34:47 +08:00
2026-08-16 12:03:13 +08:00
2026-06-09 22:09:13 +08:00
2026-05-23 00:10:56 +08:00