While you are editing records directly in Salesforce, you may receive an error message that reads "The record you were editing was modified by Backstory during your edit session."
​
This issue is a Salesforce-side process called Collision Detection, which locks records when any process is active concerning that record. It serves as a safeguard to ensure data integrity and prevent data loss.

Any integration that adds or updates records in Salesforce can cause this error. Before opening a ticket with Backstory Support, we recommend checking out this Salesforce documentation: Record Locking Cheat Sheet

In some cases, Backstory may be the culprit; in other cases, it could be another integration running in your Salesforce instance. As this function is not configurable, the solution is to find ways to work around this process. Check out our best practices below.

The likelihood of a collision increases as the frequency of synchronization increases. For example, customers who sync six times an hour are more likely to encounter conflicts than customers syncing once an hour, as there are six times as many processes occurring every hour.

Here are some recommendations on ways to minimize the pain of collisions for end-users:

In both cases, a trade-off must be considered. If syncing very frequently is critical to the business process, educating users on the recommended workaround might be the best option. If the speed of sync is not a factor for your organization, syncing once an hour might not be an issue.