Find approved messages that were pushed before LinkedIn email associations were configured — so no message goes missing.
TEMP TOOL
Trace a Batch — Find Out Where Every Message Landed
When to use this
Use this when the numbers don't add up — e.g. you submitted 90 messages but only
saw 23 show up for customer review. The orange scanner below only looks at messages
that are still approved and not deleted, so it will show "no orphaned
messages" even when most of your batch was auto-deleted (superseded duplicates,
HeyReach duplicate auto-delete, exclusions, etc.). This tool queries every
connect_queue record for a BDR — deleted or not — in a time window, and
sorts each one into exactly what happened to it.
Defaults to the last 24 hours for the selected BDR. Widen the range if you're not sure exactly when you submitted.
Fetching every connect_queue record for this BDR...
Fix Records After BDR Email Change
When to use this
After changing a BDR's primary email in Email Controls, historical records
(connect queue, activity, HeyReach data, etc.) still reference the old address.
This tool scans those collections and rewrites the email field so the records
stay linked to the correct BDR. Routing/config collections are also re-synced.
Updates linkedin_accounts, linkedin_email_associations,
and harvest pool collections — fixes the "LinkedIn Email Not Configured" warning
and restores correct HeyReach routing for the new address.
Records that will be updated
Collection
Field
Records Found
Total records to update
0
This rewrites Firestore records — it cannot be undone
What this page does
Scans connect_queue for messages that were approved/pushed within the date range you choose.
Flags any whose BDR had no LinkedIn email association at the time (or still doesn't), meaning they may not have been routed to HeyReach correctly.
Shows you the full message text and contact info so you can manually re-send or take action.