Keeping a record.
WHAT TO RECORD
What each job does Why it exists What schedule it runs on What depends on it What happens if it stops
WHY
With more than two, you will not remember.
If something fails, knowing what should be running is where diagnosis starts.
WHERE TO KEEP IT
With your site documentation, off the server.
WHAT THIS ENABLES
Recreating them after a migration Identifying a job that should not be there Handing over to someone else
THE HANDOVER POINT
Someone taking over a site with undocumented cron jobs has no way to know what is scheduled.
REVIEWING IT
Annually, and after any change.
Remove jobs for applications you no longer run.
WHAT PEOPLE FIND
Jobs for plugins removed years ago Duplicates from a migration Jobs nobody can explain
That last category should be investigated before removal.
