Warning Setup Process Not Completed

When opening org credentials or any other record in Copado, you may come across the error below:

"Warning SETUP PROCESS NOT COMPLETED ACTION REQUIRED: You have not completed setup process to use Copado fully. Please click the below link and follow the instructions carefully."
User-added image


This error may be displayed in the following situations:

  1. If you don’t own org credentials in the org where Copado is installed.
  2. If you own org credentials in the org where Copado is installed but the org credentials are not validated.
  3. If you own and have validated more than one org credential in the org where Copado is installed (duplicate org credentials).
  4. You create and validate your own org credential. Later on, you create an org credential for another user and click on the Authenticate button and the other user enters the login details (duplicate org credentials).

The solution for #1 and #2 is to create and validate org credentials with your user in the org where Copado is installed.

The solution for #3 and 4# is to remove the duplicate org credentials and keep the originals created for your user. You need to make sure that you only own one org credential in production and it's validated by you. Other users must create and validate their own org credentials in production. Please make sure the record is not in the recycle bin.

Warning: If the org credentials that you are going to remove are currently being used, you will need to update the records with the new org credentials as soon as they are created.
Once they are deleted, check the SFDC Org ID field of the original org credential in production. There shouldn't be any ‘_number’ at the end. If you can see ‘_number’ at the end, you need to remove it. Open the developer console. Enter the following query: Select Id, copado__SFDC_Org_ID__c FROM copado__Org__c WHERE Id='enter the org credential id here'. You will see the SFDC Org ID field, edit the field, remove the ‘_number’ and save it.

Check the Org Credentials record again. If you see the warning message, validate the org credentials again without creating new org credentials. The error message should be gone.


How did we do?