Incident reported: 5 January
What's the issue?
Since 5th of January 2025, 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.
Instance | Resolved? |
CS63 | Yes |
CS215 | Yes |
DEU114S | Yes |
SWE60S | Yes |
USA250S | Yes |
USA258S | Yes |
USA260S | Yes |
USA262S | Yes |
USA270S | Yes |
USA28S | Yes |
USA420 | No |
USA480 | No |
USA534S | Yes |
USA654S | Yes |
USA 656S | Yes |
USA660S | Yes |
USA666S | Yes |
US668S | Yes |
USA670S | Yes |
USA672S | Yes |
USA682 | No |
USA732 | No |
USA754S | Yes |
USA756S | Yes |
USA888S | No |
We will continue to update this list as we gain more information.
What's the cause?
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.