Deployment of Extended Context Definitions

Here are the scenarios where the deployment of extended context definitions aren’t supported.

• Deployment of context definitions from the current Summer ’26 release org to an older version such as Spring ’26 release org.
• Attempts to modify (update or delete) existing custom nodes and attributes for a context definition will fail when your context definition is in an active state. To apply these changes, you must first deactivate the definition on the target org, make the necessary modifications, and then reactivate the context definition.
• The activation or deactivation of a context definition as an action within a deployment package isn’t supported and will cause the deployment to fail. These state changes must be performed as a separate, manual step in the target org, outside of the deployment process.
• Changing the default status of a context mapping as an action within a deployment package isn’t supported and will cause the deployment to fail. Any change to a mapping's default status must be performed as a separate, manual step in the target org.