Initial post: 4 Jan 2024, 17:00pm UTC
Last updated: 2 Feb 2024, 22:00pm UTC

As of 2nd Feb 2024, 22:00pm UTC, there has been a report of this issue, so it is possible this has not been fully resolved yet.

Since 22nd of January 2024, Gearset was made aware of slowness in the retrieval of metadata using the Salesforce Metadata API, similar to what we reported on the 4 Jan.

So far we have confirmed that the following Salesforce instances are facing this issue.

We will continue to update this list as we gain more information.

When running a test using Workbench (an independent application), which uses the same Salesforce Metadata API as Gearset, users are able to replicate a longer than expected retrieval time on the same orgs with the same metadata.

We are asking all users to run these tests to allow us to confirm if the cause of their comparison retrieval issue is the Salesforce Metadata API.

If the retrieval is much faster in Workbench then it can be useful to start the comparison again to see if it is a transient issue. If the retrieval is fast in Workbench but still slow in Gearset then please let us know through the in app chat.

As of 5th Jan 2024, 09:00 UTC, there have been no further reports of this issue, and the slow retrieval of objects over the Metadata API is believed to be resolved.

Since 3rd of January 2024, Gearset was made aware of slowness in the retrieval of metadata using the Salesforce Metadata API.

So far we have confirmed that the following Salesforce instances are facing this issue.

We will continue to update this list as we gain more information.