The panel scheduler runs WithSeconds(), whose parser rejects a standard five-field crontab such as "30 8 * * *". An admin who typed one into the Telegram/Discord notify time or the LDAP sync schedule saved it without error, AddJob then failed at startup, and the job silently never ran. Admin-typed schedules now go through internal/util/cronspec, which takes an optional seconds column plus the @descriptors and hands the scheduler a parsed cron.Schedule. CheckValid rejects an unparseable schedule on save, and a stored legacy value falls back to the job's default instead of dropping the job. |
||
|---|---|---|
| .. | ||
| common | ||
| cronspec | ||
| crypto | ||
| json_util | ||
| ldap | ||
| link | ||
| maskcompat | ||
| netproxy | ||
| netsafe | ||
| random | ||
| reflect_util | ||
| sys | ||
| totp | ||
| version | ||
| wirecodec | ||
| wireguard | ||