The AI cron builder turns “every weekday at 02:30, run the backup and keep a log” into a correct crontab line — with output redirected to a log and flock so two runs never overlap. It also lists the next five run times and writes the equivalent systemd .service and .timer units.
AI answers can be wrong. Read every command before you run it, and test on a non-production server first. Your input is sent to our AI provider (srvScripts AI) to write the answer. srvScripts does not log your input; the answer, which can quote it, is cached for 24 hours so a repeat question is answered instantly. See the privacy policy.
Table of Contents
It saves the classic cron mistakes: a missing PATH, an unescaped percent sign, the wrong day-of-week number or a timezone surprise.
How to use the AI cron builder
- Describe when the job should run and what it runs.
- Optionally set the server timezone.
- Press Build schedule and paste the line into crontab -e, or install the systemd units.
What you get
- The crontab line with logging and flock.
- The schedule in plain English and the next five runs.
- A systemd timer alternative with Persistent=true.
- Common mistakes to avoid for this job.
Worked example
Example: “Every weekday at 02:30, run /root/backup.sh and keep a log.” The builder returns 30 2 * * 1-5 with flock and output appended to /var/log/backup.log, lists the next five run times, and writes a backup.service and backup.timer pair with OnCalendar=Mon..Fri 02:30 and Persistent=true.
Tips for better answers
- To check an existing expression use the cron expression helper; to write service units use the systemd unit generator.
Pair it with the AI script generator to write the script the job runs.
Privacy and limits
Before anything is sent, srvScripts removes private keys, passwords, tokens and API keys it recognises. With the box ticked it also swaps public IP addresses and e-mail addresses for placeholders, which lowers the risk when you paste real logs. The masking is automatic and best effort: it can miss names, hostnames, keys or other customer details, so remove anything confidential before you paste. Your text goes to our AI provider only to write the answer. srvScripts does not save your input as a record of its own, but the masked input is sent to the AI provider to produce the answer, and the answer, which can quote parts of your input, is cached on our server for 24 hours so a repeat question is answered instantly, and is then deleted. The provider’s own API data terms apply to what it receives. Without an account you get 5 runs a day, a free account gets 15 and srvScripts Pro 200, with larger inputs.
At a glance
Official documentation: crontab(5) manual, systemd.timer manual.
Frequently asked questions
Cron or systemd timer — which should I use?
Timers log to the journal, catch up after downtime with Persistent=true and avoid overlap natively. Cron is simpler and works everywhere, including cPanel user crontabs.
Why does my cron job work by hand but not from cron?
Usually PATH or environment differences. The AI cron builder uses full paths and shows what to set.
Does the AI cron builder support the cPanel Cron Jobs page?
Yes — use the five time fields and the command from the crontab line.