Removing a card deletes the underlying opportunity row, records an unlink so the estimate auto-matcher will not re-attach the job, records a global pipeline removal so the auto-sync will not re-link it to any other matching contact, and hard-deletes the lead row with a durable cross-device suppression so the CRM sync cannot re-ingest it. The estimate stays in Estimates and the contact stays in Contacts.
Also called: deleted lead came back · zombie card · remove a deal · card keeps reappearing
- 1Estimate-backed cards: delete the opportunity row, record an unlink and a pipeline-removal marker
- 2Lead cards: record a removed-contact marker the board filters directly
- 3Both: hard-delete the lead row and write a durable suppression key so the sync never re-ingests
- 4A deliberate re-link clears both the unlink and the removal markers
Removing a card did not stick, and it failed three separate ways. Hiding it on screen was overwritten on the next refresh, since the board is rebuilt from the underlying record rather than from what was last displayed. Pushing it to an off-board stage failed because the stage logic refused to move a contact backwards. And an early version left both the record and the CRM contact intact, relying on a flag stored in one browser, so the lead regenerated on the next device. Removal now deletes the canonical record and writes permanent markers, so no sync, poll or auto-linker can resurrect it.
- Removals that only hid a card locally
- Auto-linkers resurrecting a removed job through a different contact
- CRM syncs re-ingesting a deliberately deleted lead
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →