Studio workday-out-soap Step: "Web Service or Version Is Invalid for the Requested Operation"
The error Worker null does not exist.Worker does not exist.
Caused by: The web service or version is invalid for the requested operation
What it means
The integration is calling a valid Workday web service operation, but the workday-out-soap step is pointed at the wrong application/version combination, so Workday cannot find that operation on that endpoint. It fails before any business logic runs, which is why fixing the payload data (like using a real worker ID) does not help.
Troubleshooting
- Open the failing Studio integration's workday-out-soap step and check the configured Web Service application name and Version number.
- Compare that version against the WSDL or API Explorer entry for the exact operation you are calling - application names like Integrations, Human Resources, or Staffing each expose a different operation set per version.
- Log the fully-assembled request right before the web service step to confirm the operation name in the XML matches what that application/version actually supports.
- If the integration was cloned from an older template, check whether Workday retired that operation in the version you are pinned to - retired operations throw this exact fault.
⚡ Quick fix
Update the Web Service Version field in the workday-out-soap step to the current version that exposes the operation you are calling, then re-run.
✓ Permanent fix
Pin integrations to a specific tested application/version pair and add a release-note check to your Workday upgrade routine so version-specific operation changes get caught in Preview before they break Production.
Was this helpful?