The sync that deleted our leads every 60 seconds
The sync that deleted our leads every 60 seconds Leads were vanishing. Not bouncing, not erroring — just gone. New leads would appear in our registry, get processed, and then... nothing. The registry would quietly roll back to an older state, as if the last few minutes of work had never happened. We noticed because a lead we'd already responded to showed up as brand new, then disappeared again.…
A sync script that deleted leads every 60 seconds was discovered in a pipeline. Leads were vanishing silently, reappearing as new, and the registry would roll back to an older state. The sync job was pulling outdated data from the public server instead of the VM where the parser actually ran. The script still referenced the old architecture, even though the parser had been moved.
The sync job was perfectly reliable but executing the wrong instruction. The issue arose because the sync job was unaware of the architecture change. The fix was to make the VM the source of truth for the lead registry and update the sync job in the same commit as the move. The checklist includes searching for old assumptions after moving a pipeline stage, trusting only the source of truth (the VM in this case), and watching for symptoms of the sync fighting the source of truth.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
