Originally we only made the autostart backend a 3-valued cron string, but most cron libraries only handle the traditional 5-valued cron string. This would allow us to reduce some complexity in the frontend code.

I think so, but only if the backend was validating that we always received a full valid 5-value cron string (with optional timezone). The only reason it would help is so that I know I can pass these strings directly from the backend into JS cron libraries for validation and display.

I plan on making the C/U form a set of widgets that under the hood produce a cron string. So imagine an input for your timezone, one for time and another with the 7 days of the week that you select/deselect.

Originally posted by @vapurrmaid in #991 (comment)