A field that flips back every few minutes
How you'll know: A rep fixes a title or phone number in Salesloft, and the old value comes back after the next pull.
Fix: Both systems are allowed to write the field and Salesforce has priority. Decide which system owns each mapped field and let only that one send updates.
New people that never reach Salesforce
How you'll know: The sync log shows failures on create, often the same error over and over.
Fix: A required Salesforce field or a validation rule is rejecting the record. Map a value for the required field, or adjust the rule for the integration user, then retry from the log.
Duplicates between leads and contacts
How you'll know: One person is a lead and a contact in Salesforce, and Salesloft activity lands on the one nobody looks at.
Fix: Pick the matching rule that suits how your team converts leads, merge the existing pairs, and keep the rule consistent from then on.
An automation rule that ignores people who already qualify
How you'll know: You build a rule for a stage or field value, and the hundreds of people already sitting at that value are never enrolled.
Fix: Salesloft's automation rules fire when data changes, not on what's already there. Enroll the existing group once, by list or through the API, and let the rule handle new changes.
Activity on the contact, nothing on the opportunity
How you'll know: Your Salesforce opportunity report can't say which cadence produced the deal.
Fix: Tasks attach to the lead or contact. Getting the sourcing cadence onto the opportunity takes logic that runs when the opportunity is created, which is a build, not a setting.