Connectivity Investigations and Troubleshooting

Since so much of Copado's behavior leverages internet connectivity and may include additional platforms such as Salesforce, Git Providers, and ALM Providers, we recommend users bookmark the following websites to monitor connectivity when using Copado. The following links are accessible for all users to utilize:

1. The Copado Status site is used to monitor Copado systems status; It offers a wide variety of notifications to subscribe to including Email and SMS 

2. The Salesforce Status site is used to monitor Salesforce instance statuses; It offers a wide variety of notifications to subscribe to including Email and SMS
a. It’s good to subscribe to notifications for Instance that Copado is on as well as Instances that each Pipeline Environment is on
3. Additional status sites below will help in monitoring statuses and downtime too: 

4. - Use this link to check a user's local connectivity

If you have checked the connectivity links above, and they do not resolve the issue you are encountering, please review the following as well:

1. Check Session Settings:
a. In the Org where Copado is installed
b. In Org Committing
c. In the Org Deploying from and in the Org Deploying to
2. Check IP Whitelisting for Copado Backend:
a. At Org level in Network Access
b. At Profile level, if users have Profile IP Login restrictions
3. Check Org Credential User's Profile:
a. In the Org where Copado is installed, 
b. In the Org Committing, in the Org Deploying from and In the Org Deploying to
1. Oftentimes users will have a Copado Integration User on a limited Profile in Production (where Copado is Installed), which is fine, but, after Refreshing a Sandbox, users forget to update the Copado Integration User back to the native System Administrator Profile in the Sandbox. This causes Metadata access problems for Commits, Promotions and Deployments
4. Check that all default Org Credentials are valid and properly shared
5. Check that the User's Org Credential for Production (Org where Copado is Installed) is valid
6. Check that the Git Repository record is valid and Authenticated
7. Check that Git Snapshot records have proper Git Permissions and valid Org Credentials
8. Metadata filters on Git Snapshot records may be causing unexpected behavior
9. Exclusions in the .gitignore may have been forgotten and are causing behavior with new Metadata
a. For example, an Org initially chooses to exclude Reports and Dashboards in the .gitignore, since all of their users are authorized to create Reports and Dashboards at-will in Production, but they forgot this exclusion in the .gitignore and are now attempting to Commit/Promote/Deploy a new Lightning Home Page that includes a Dashboard or an updated Page Layout that includes a new Report chart
10. Check the YAML added to the Pipeline. This may be causing unexpected behavior.


If you are still encountering issues after reviewing this article, please create a support case for further investigation.

How did we do?