Bug Fix

Fix lead sources re-archiving overnight and understated contact counts

What We Fixed

In Settings > Lead Flow, a lead source that was manually unarchived could silently return to the archived state after the nightly maintenance job ran — making sources fed mostly by CSV imports effectively unusable. The same sources also displayed a contact count far lower than the number of contacts actually using them.

Both problems shared a root cause: contacts added through CSV import bypass the live routing pipeline, so they never advanced the source’s “last activity” timestamp or its stored contact count. As a result the source looked inactive to the auto-archive job and undercounted its contacts.

Now:

  • Unarchiving a source that has contacts resets its activity timer, so it stays active until you archive it again.
  • After a CSV import, each affected source’s contact count and activity timestamp are recalculated from its actual contacts.
  • A one-time backfill corrects the counts and timers on existing sources, so already-affected sources are fixed without needing another import.

Note: archiving remains the supported way to remove a lead source; there is no separate delete action.