Drift - Salesforce Error “Couldn’t find/create suitable record after retry”

Sep 21, 2026
Knowledge

Created Date

10/13/2026, 12:01 PM

Last Published Date

9/21/2026, 2:41 PM

Article

This error is usually due to a lead getting stuck in the MAP, or taking longer than expected to flow through the MAP to Salesforce. That results in Drift not being able to find the record in Salesforce to attach the chat or meeting activity to.

Here’s how to troubleshoot this and future occurrences:

1. Look up the contact record, and find the conversation through their activity timeline. You can also search for the lead’s email in conversation analysis.
2. The important convo items to check:

a. Did we gather all of the required information to push a lead through the MAP to SFDC? Determine this by checking the data gathered in the contact record and the conversation. If not, that could explain why it got stuck. Check if this is a one off or a playbook setup problem.

b. When was the conversation closed and synced?

i. Check when the conversation closed, and when we synced to the MAP via the event log (ELQ in this example)
ii. Drift will attempt to sync to SFDC when the convo closes, and then again after your set retry time of [#] minutes. You can see in the SFDC event log when the retry failed, and that’s when you’ll get the email notification.

c. When, if at all, was the lead created in SFDC? If it was there before the sync retry time (seen in the SFDC log), then please send a brief summary of the steps taken above, and most importantly a screenshot of that lead’s SFDC creation date, to our Support team for further investigation.

i. If the lead was created in SFDC after our retry time, please look into why it was delayed in getting through the MAP to SFDC.

Title

Drift - Salesforce Error “Couldn’t find/create suitable record after retry”

URL Name

Salesforce-Error-Couldn-t-find-create-suitable-record-after-retry

Drift - Salesforce Error “Couldn’t find/create suitable record after retry”

Information

Fields