systemd timers instead of cron
Cron is fine until a job fails silently at 3 a.m. Timers log to the journal, can depend on the network being up, and catch up on runs that were missed while the machine was off.
[Timer] OnCalendar=*-*-* 03:30:00 Persistent=true RandomizedDelaySec=10m
systemctl list-timers shows when each job last ran and when it will run next, which is the question you always end up asking about cron.