Issue
As of 08/17/2022 myself and my Development/QA team has been running into an issue with SF Workbench when using API v55.
We are deploying Service Cloud Voice (SCV) Contact Center with features that are in v55
The following error is thrown, as soon as you login with your SF credentials
UNKNOWN ERROR: SOAP-ERROR: Parsing WSDL: Couldn't load from 'soapclient/sforce.550.partner.wsdl' : failed to load external entity "soapclient/sforce.550.partner.wsdl"
Related Past Tickets
- I found this related ticket in the past when this occurred in API v45
Version 45 corresponds to Spring '19, it was not available in production on the moment when this question was opened, but should be available now, since all the production organizations should have already migrated to Spring '19.
- I found this other related ticket in the past when this occurred in API v42
I'm seeing the same issue. It can be solved by logging out of Workbench entirely and then re-logging in with the API version set to 41. You have to end the session and start over; you can't change the API version in Workbench settings once you get this error.
- I found this other related ticked in the past when this occurred in API v34
From the discussion it sounds like the problem might be intermitent and caching related. I'd suggest posting your experience into that discussion. Reverting to API v33.0 in workbench avoids the problem.
Temporary Workaround (Not Ideal)
The error goes away when I use API v54, though we are required at this time to use v55
Any estimates on how long this usually takes to resolve?
Additional Details && Attachments
- SF Workbench URL I am Using
Screenshot of Issue in SF Workbench using API v55Image may be NSFW.
Clik here to view.
Ticket Not Related/Not Duplicate
- SF Workbench - API Version - v55 Not Appearing
- This question was actually asked by me a month ago, this is a different issue where the dropdown to select API Version in SF Workbench did not have a value of v55 This has been resolved since and was able to select v55 and use the deploy feature as we need without issue