Upgrade of Extended Context Definitions

When extended context definitions don’t work accurately after your Salesforce org upgrades to the Summer ’26 version, it’s because the automatic upgrade of context definition wasn’t completed. During an automatic upgrade, custom artifacts in extended context definitions could conflict with that in a standard context definition.

To fix this issue and complete the sync, click Sync Now on the Custom Definitions tab of the Context Definition page to complete the sync process.

Here are other scenarios where the auto-sync for extended context definitions fails, along with the recommended workaround solutions.

• The auto-sync process for an extended context definition will fail if the user running it lacks the necessary permissions to copy records. To resolve this issue, an administrator with Context Service Admin permissions must run the process instead. The administrator can complete the sync by clicking Sync Now for the selected extended context definition.
• If you encounter an error indicating that the maximum limits for attributes and nodes have been exceeded, you will be unable to add new ones. To resolve this issue, you can either delete unused nodes and attributes to free up space, or contact Salesforce support for assistance.
• If you’ve got corrupted context definitions due to invalid mapping records, we recommend reaching out to Salesforce support for help.