Contract Lifecycle Management / Salesforce Contracts: 'We couldn't fetch the context definition name' error for non-admin users on Update Contracts and contract status change

Resolve the error by assigning the Context Service Run Time User permission set license to every non-admin user who creates, updates, or changes the status of contracts, and by granting the Salesforce Contracts permission set so the user can read Context Use Case Mapping records.

Cause 1: Non-admin user is missing the Context Service Run Time User permission
1. Navigate to Setup > Users > Users and click the affected user's name.
2. On the user detail page, click the Permission Set License Assignments related list, then click Edit Assignments.
3. Select Context Service Run Time User and click Save. (System administrators have this access by default; non-admin users must be assigned the license explicitly.)
4. Return to the user detail page and click Permission Set Assignments > Edit Assignments.
5. Add the Context Service Run Time User permission set and click Save.
6. If the same user must edit context definitions or context use case mappings, also assign the Context Service Admin permission set license and permission set using the same path.

Cause 2: Non-admin profile or permission set is missing read access to Context Use Case Mapping
1. Navigate to Setup > Permission Sets and open the permission set assigned to the affected users (for example, the CLM user permission set).
2. Click Object Settings, locate Context Use Case Mappings [ContextUseCaseMapping], and click Edit.
3. Set Object Permissions to Read for non-admin contract users; set Read, Create, Edit, and Delete for contract administrators.
4. Under Field Permissions for Context Use Case Mappings, set Read Access for every field, including Reference Object Name, Reference Object Record Type, Target Object Name, Target Object Record Type, Target Object Custom Field Name, Context Definition Name, Mapping Type, Mapping Name, and Use Case Type.
5. Click Save.

Cause 3: Context Use Case Mapping record is missing a row with Target Object Record Type set to null (Update Contracts only)
1. Navigate to Setup > Contract Lifecycle Management > Context Use Case Mapping.
2. For each Reference Object Name used by your org (Opportunity, Quote, Order, or any custom source object), confirm at least one record has Use Case Type = Update Contract and Target Object Record Type left blank. The Update Contracts action does not consider the target record type and requires this null-record-type mapping to resolve the context definition.
3. If the row is missing, click New, set Reference Object Name, Target Object Name = Contract, leave Target Object Record Type blank, set Context Definition Name (for example, ContractsContextDefinition), Mapping Type = Hydration, Mapping Name (for example, OppToCntrHydrationMapping), and Use Case Type = Update Contract. Click Save, then repeat for Mapping Type = Persistence using the matching persistence mapping name.

Verification
Confirm the issue is resolved by logging in as the affected non-admin user, opening a Contract record that was previously failing, clicking the standard Update Contracts button, and confirming that the contract updates without the "We couldn't fetch the context definition name" error. Then change the contract Status [Status] field to a different picklist value and save to confirm the status change completes successfully.