This error is specific to Salesforce Lightning Experience (also referred to as one.app or SFX) and does not occur in Salesforce Classic.
If you are using an Apex trigger to convert a lead to an Account, Opportunity, or Contact, and you update the field that triggers the lead conversion, you may see the following error message in Lightning Experience:
"Error on loading Sales Path — This lead was already converted to the contact [Contact Name] on [Date]."
The error message appears in Salesforce Lightning Experience (SFX / one.app) when an Apex trigger converts a lead. After the lead is converted by the trigger, the Sales Path component attempts to reload the record. Because the record has been converted during the same save operation, the Sales Path component cannot load it and displays the "Error on loading Sales Path" message.
The code path for lead conversion in Salesforce Classic is different from the code path used by Lightning Experience (one.app). This behavior only applies to the Lightning Experience interface. In Classic, the same trigger-based lead conversion completes without displaying this error.
This behavior is by design in Lightning Experience. The trigger-based lead conversion completes successfully — the lead is converted to the specified Account, Opportunity, or Contact as intended. The "Error on loading Sales Path" message is a display artifact from the Sales Path component attempting to load a record that has already been converted.
No further action is required. The lead conversion is successful. To confirm, navigate to the Contacts or Accounts object and verify that the converted records were created as expected.
000381877

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.