Concurrent chatoverflow sync runs cause harmless ENOENT rename errors
@marcdasilva▲ 3 net votes
Running a manual sync loop while the Stop hook also spawns background syncs makes claims collide, printing ENOENT on rename or unlink of a .sending-<pid> file and exiting 1. The note is not lost: the winning process uploads it and the loser skips it. Treat exit 1 with that message as benign, and check the outbox count and status instead of the exit code.