Gearset uses the Metadata API to retrieve and deploy your metadata. If you are observing slow performance with comparisons in Gearset, the Metadata API is usually the first potential cause we want to evaluate. We will work with you to gather evidence to help understand whether the Metadata API is having an issue, or if this is something else that Gearset can control (and fix).
Here are the troubleshooting steps you can take to help gather evidence to pinpoint the root cause of the slow comparisons:
Run a test with Workbench. Workbench uses the same Metadata API that Gearset uses, and by retrieving metadata via Workbench, we can remove Gearset entirely from the equation to only test the Metadata API performance.
By comparing an org with itself as the source and target, you can isolate the org to work out which (source or target org) is the slow one. Test that org with Workbench.
Instructions here. It's important that the package that you retrieve from Gearset and via Workbench match, so that we have a like-for-like comparison for retrieval speeds with the Metadata API. Please note the retrieval duration for both Gearset and Workbench.
Check what instance your Salesforce org is on. Often, only a small segment of Salesforce instances may be experiencing issues (which they share on their trust page). By tracking what instances are experiencing issues, we can build a better picture across our user based to understand the issues. You can find this information under
Company informationin your respective Salesforce org.
It can sometimes be important to confirm what API version your org is on, as well. When orgs are upgraded to the latest Metadata API version, this can sometimes cause initial friction as the kinks are worked out.
You can find this API information here.
Sharing all of this information with us via the in-app chat is the best way we can record this, and expedite a resolution. If the evidence is pointing towards a Gearset issue, we will raise this internally and work to resolve the issue as soon as possible to get those deployments going again!
If the evidence is pointing towards the Metadata API being the root cause, we'd likely ask you to open a support case with Salesforce support. This lets them know an issue is ongoing, so it can be resolved.
If you share your case number with us, that can help us gather all of this evidence together so we can also report this, and demonstrate the breadth of the problem.Here's the information to share with us:
Retrieval time duration using Gearset of a single org
Retrieval time duration using Workbench of a single org
The org's Salesforce instance
The org's current API version
Salesforce support case number, if applicable
Thank you for helping make Gearset better!