Workday Out REST Connection Reset From Leftover HTTP Headers
The error An I/O error occurred sending to https://wd2-impl-services1.workday.com/ccx/service/customreport2/TENANT/OWNER/ReportNAME?ApplicationID=ExpectedValue: Connection reset (esbHttpRequestId=1c074058-7170-443e-1c68-455b2d343a5c)] Caused by: [javax.net.ssl.SSLException: Connection reset] Caused by: [java.net.SocketException: Connection reset]
What it means
A Workday Out REST step fails with a generic connection reset error even though the endpoint and credentials are correct. In an assembly that makes more than one outbound HTTP call, headers set for an earlier call, such as a third party OAuth token request, can carry over into the Workday Out REST call and break the TLS handshake.
Troubleshooting
- Confirm the assembly makes more than one outbound HTTP call before the failing Workday Out REST step, especially calls to third party or OAuth endpoints.
- Check whether an earlier Set Header step sets headers without clearing prior values, since mediation message headers persist across steps unless explicitly cleared.
- Add a Set Header step immediately before the Workday Out REST step with Clear All Headers selected, then only re-add the headers Workday actually needs, usually just Content-Type and Authorization.
- Re-run the integration and confirm the connection reset no longer occurs. If you need to identify the exact offending header for other steps, re-add headers one at a time until the failure returns.
⚡ Quick fix
Insert a Set Header step with Clear All Headers checked directly before the failing Workday Out REST call.
✓ Permanent fix
Treat mediation message headers as shared state across the whole assembly: reset headers explicitly before each outbound call rather than assuming they reset between steps, especially in assemblies that call multiple different external systems.
Was this helpful?