To prevent overlapping, Laravel uses files with a name "schedule-xxxxxx"where xxxxxx is a hash of a command that should not overlap with itself. Files are hosted in storage/framework. If something goes wrong during the execution of the command, the file cannot be deleted, as a result of which the command will not work again.
What OP did - renaming a command is one solution. A bit easier - deleting mutex files:
rm storage/framework/schedule-*
But none of them is a real solution, if you are not 100% sure that the team will work correctly from now on. Otherwise, the problem may recur soon.
I ended up doing something similar in my cron file:
find /var/www/storage/framework/ -name schedule-5b904de82f094302106f83418c5adb01 -mmin +20 | xargs -I{} rm {}
, . 5 . , 20 , , - , .
, , , , , -. , , , - , , . , . , .