Sometimes cron is working just fine but the script or command you want it to run just fails silently, causing you to bark up the wrong tree.
In such cases I find it useful to wrap the target within another short script, which outputs some visible debugging code (including output of date) and use redirection to ensure I get some evidence to inspect. If the target is a script, wrapping around a sh -x can help further.
The crontab entry (always edit with crontab -e) could look like this:
00 14 * * * (sh -x /tmp/my_wrapper_script) >> /tmp/debug.log 2>&1Inspect /tmp/debug.log and its timestamp. If it's empty, non-existent or the timesamp isn't shortly after 14:00 (in this example) you may have a cron issue, otherwise you need to debug the actual target action and cron is working just fine!