errors / core-connectors / core-connector-httppost-failed-soap-fault
Core Connector Delivery Fails: "HTTPPost Failed With SOAP Fault"
The error HTTPPost failed with SOAP Fault
What it means
Core Connector successfully generated the output file, but the delivery step - pushing that file to the receiving endpoint over HTTP/SOAP - was rejected by the target server. This is a transport/connection problem, not a data problem; the integration ran fine right up to the point of sending the file.
Troubleshooting
- Confirm the output file was generated correctly (check Integration Events - if the file exists and only delivery failed, mapping/XSLT is not the issue).
- Check the delivery step's security/auth settings - a SOAP Fault on HTTPPost is commonly a rejected handshake, wrong Basic Auth credentials, or an endpoint that expects no security when the connector is sending some (or vice versa).
- Verify the destination URL is reachable and correct (protocol, port, path) - paste it into a browser to confirm it resolves and hasn't expired or rotated.
- Check whether the vendor changed their endpoint's security requirements (cert renewal, TLS version bump, IP allowlist) - this error often appears right after a vendor-side change even though nothing changed on the Workday side.
⚡ Quick fix
Temporarily set the delivery security to match exactly what the receiving endpoint expects (or "No Security" only when testing in a non-prod tenant) to isolate whether it's a credentials problem.
✓ Permanent fix
Document the delivery endpoint's exact auth/security requirements per vendor, and re-verify them whenever the vendor reports a change on their end - this error is nearly always receiving-endpoint config drift, not a Workday-side one.
Was this helpful?