Sometimes, you may encounter an error on your CI job when viewing that job's activities on the CI dashboard page.
Here's a list of some known errors, and what the resolution for them is:
Does the error look like this: "An unknown error occurred during problem analysis"?
Does the error look like this: "An unknown error occurred during problem analysis"?
An example of how the error may be displayed on the CI dashboard when your hover your mouse over affected CI job:
How to resolve this issue?
Are you promoting a PR via a CI job within your Pipeline set up?
And is the error happening on that specific PR?
If the answer to the above is yes, please get in touch with our support team via in-app chat. We'll be able to check the logs for the (child) CI job run specific to that PR promotion.
It will help us troubleshoot if you provide us with your CI job ID, which you can find on your CI dashboard:
Possible root cause(s)
From previous use cases we've investigated, this issue may be related to our problem analyzers detecting multiple (or duplicate) metadata components within a specific metadata component in your feature or promotion branch.
We advise to check if the metadata components of which changes you're promoting via PR may have been amended in the target org of the CI job.
It's possible that problem analyzers are detecting an issue due to differences between the metadata components found in the long-lived environment branch (CI source) and the target org (CI target).
Does the error look like this: "An unknown error occurred while logging in. Please try re-authorizing the org, or contact support if you need assistance with this issue."?
Does the error look like this: "An unknown error occurred while logging in. Please try re-authorizing the org, or contact support if you need assistance with this issue."?
An example of how the error may be displayed on the CI dashboard when you hover your mouse over affected CI job:
How to resolve this issue?
Usually, this error indicates a problem with Gearset accessing the access token for the org that is set as the target of the CI job.
For example, the access token may have expired and therefore we are unable to access the org (which wouldn't allow you to run the CI job deployment to that org).
Re-authorizing that org's connection within our app should help you resolve this issue.
You can follow the steps from below article if you need more guidance on how to re-authorize the org connection:
Common authentication and comparison errors
If this doesn't help you resolve the issue, please get in touch with us in the in-app chat.
Note: If you're not the owner of the affected CI job, the re-authorization would need to be done by a team member (on your Gearset team) who owns this CI job connection.
In other words, the re-auth need to be done on the CI job owner's Gearset account.