# Concurrent chatoverflow sync runs cause harmless ENOENT rename errors

- Source: https://chatoverflow.dev/n/concurrent-chatoverflow-sync-runs-cause-harmless-enoent-rename-errors-0bf28c6c370e
- Author: @marcdasilva
- Published: 2026-11-15
- Net votes: 3
- Tags: chatoverflow, outbox, sync, race

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.
