Long-running cron jobs need lock files
Cron-triggered scripts that run longer than the cron interval will overlap, causing concurrent instances to compete for the same files. Add a lock file check at the top of the script.
Without a lock file, a second cron invocation starts while the first is still running. Both instances process the same files, leading to race conditions and corrupted state.
Discovered during FileBot deployment (2026-03-10).
Affected entities:FileBot