Core Connector SFTP-Out Delivery Fails with "Connection Timed Out"
What it means
The core connector successfully generated its output file but couldn't hand it off to the receiving SFTP server. Workday's outbound delivery step, the SFTP-Out transport, never got a response from the destination host, so the connection attempt timed out before authentication even completed.
Troubleshooting
- Confirm the integration itself ran successfully and the output file was generated, so you know the failure is happening at delivery, not data processing.
- Check whether the destination SFTP host name and port in the transport configuration are still correct; a rotated hostname or decommissioned server produces this exact symptom.
- Ask the receiving-server owner whether Workday's outbound IP range is currently allow-listed on their firewall, since a dropped or expired allow-list entry causes a silent connection timeout rather than a clear auth rejection.
- Verify the SFTP credentials (and any client certificate) on the transport haven't expired or been rotated on the receiving end without a matching update in Workday.
- Re-run a single test integration after confirming firewall and credentials to isolate whether it was transient network flakiness or a persistent config problem.
Re-launch the integration once the receiving-server owner confirms the SFTP host is reachable and Workday's IP is allow-listed; a one-off network blip will often clear on retry.
Add a monitored connectivity check, or a scheduled low-risk test transfer, between Workday and the destination SFTP endpoint so a firewall or credential change on the receiving side surfaces before a real integration run fails, and document who owns that SFTP server so troubleshooting doesn't stall on finding the right contact.