Skip to main content

Return to TX Community


Resolving common errors in Group Assignment migration or refresh



An error has occurred. {"error":"invalid_grant","error_description":"authentication failure"} This error means that the credentials you are using to migrate are incorrect. You should use the credentials for the Org you are migrating the assignment TO.

This error could also mean that the Remote Site URL referenced in Remote Connections is incorrect.
There were multiple users found with the name and alias This typically happens when the specified users have both an internal Salesforce user record and a test/student-side Community user record. Changing the name and alias on the Community User record for these individuals should resolve the error and allow you to migrate the changes.
Duplicate group name It is not possible to migrate a set of group assignments, or to refresh the trigger, if the names of different groups are the same. If the groups with the same name are duplicates, you will want to delete the extraneous groups. If they are different groups with different criteria, you'll need to rename the duplicates with a different name so that the trigger can be generated.
System.CalloutException: Unauthorized endpoint Create a new remote site using the URL included in the error message. For additional information, see: How to create a Remote Site for Group Assignment Triggers Refresh in a sandbox.
An error has occurred check deployment status You should check the deployment status of the Target Org, to view detailed error messages.
Code Coverage failure: The following triggers have 0% code coverage: TX_UniqueNicknameTests : List has no rows for assignment to SObject; Stack Trace: Class.TX_UniqueNicknameTests.setupData: line 18 column 1

The TX_UniqueNicknameTests apex class refers to a profile called 'Customer Community Plus User'. You must either:

  1. Create a profile named 'Customer Community Plus User' or
  2. Update the class to reference the Community Profile you use for the Online Application; e.g. Community User (TargetX).
CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, TargetX_SRMb.ApplicationTrigger: execution of AfterUpdate caused by: System.ListException: List index out of bounds: 0 Trigger.TargetX_SRMb.ApplicationTrigger: line 97, column 1: [] 
Stack Trace: Class.TxGrpAssgnTargetXSRMbApplicatTriggerTest.TestApplication: line 17, column 1
Any variation of this error with the object/trigger name listed is typically related to Source to Master. This can be bypassed by temporarily turning off Source to Master. Navigate to Recruitment Manager Preferences and uncheck all object rollups and then migrate/refresh the Group Assignments again.
CANNOT_EXECUTE_FLOW_TRIGGER - A flow trigger failed to execute the flow with the version ID 30146000000GarC... Errors referencing a flow require you to identify which flow or Process Builder Job is causing the error. You can use this URL:<ID in error>

Update the URL to your node and change the ID at the end to the ID in your error message.

Once you've identified the flow or process, deactivate it temporarily and then migrate or refresh.
System.QueryException: List has no rows for assignment to SObject Stack Trace: Class.TX_UniqueNicknameTests.setupData: line 20, column 1 This error occurs when the profile name in the apex class doesn't match TargetX documentation or provided code.

You should update the TX_UniqueNicknameTests apex class and replace 'Customer Community User' on lines 20 and 54 with the name of your community profile, such as '(org) Customer Community Login User'.
Comparison arguments must be compatible types: NULL, Boolean The Group Assignment criteria should be reviewed to ensure each group assignment includes a line of logic and also does not reference checkbox fields incorrectly.
System.AssertException: Assertion Failed: Expected 1000, Actual: 0 Stack Trace: Class.testCalculateProspectScore.testCalculatedScore: line 79, column 1

This error is typically caused by automations, such as workflows and process builders, that prevent creating applications within the Prospect Scoring test class. Lowering the number of applications generated in the test class resolves the issue.

Navigate to Setup and search for Apex Classes. Then update the following apex classes:

  1. dataGenerator - On line 45, change 200 to 1
  2. testDataGenerator - On line 25, change 200 to 1
  3. testCalculateProspectScore - On line 79, change 1000 to 5
Caution: These changes must be made in a Sandbox and deployed to production via a Change Set.
System.DmlException: Insert failed. First exception on row 0; first error: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, insufficient access rights on cross-reference id: 0016g000004R3Vo: []
Stack Trace: Class.TxGrpAssgnContactTriggerTest.TestContact: line 14, column 1

This error can occur during refresh or migration of the Contact trigger when the Target Org is a Partial or Dev sandbox and the Default Account ID in your Recruitment Manager Preferences lists an Account ID that does not exist in the sandbox:

  1. Navigate to Recruitment Manager Preferences and change the Default Account ID to an Account that exists in the sandbox.
  2. Save your changes.

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: TargetX_Group.GroupAssignmentContact: execution of BeforeUpdate caused by: line 3, column 40: Dependent class is invalid and needs recompilation: TargetX_Group.GroupAssignmentContact: line 1, column 8: connection was cancelled here. 

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: TargetX_SRMb_check_for_dups: Execution of AfterInsert

Resolution: Disable the Duplicate Check feature while this update is being performed, then re-enable when complete:

  1. Within the CRM click the + tab to view all tabs.
  2. Scroll down and select RM Preferences.
  3. Uncheck the Duplicate Checking box.
  4. Save your changes.
  5. Perform the load and confirm its success. Re-enable the duplicate check feature as needed.

For details on viewing Console errors, see Troubleshooting using Console Mode.


  • Was this article helpful?