A partner that still wants SFTP is asking for a contract: this directory, this file name, this encryption, this hour. Workday can meet that contract. The failures that page someone at 2 a.m. are usually a name, a key, or a step that never ran, and Workday’s own pages already name them.
SSH key, host-key, and PGP errors is the troubleshooting companion. This guide is the contract you agree with the partner before that page is needed.
Where the file is actually sent
An integration system holds the parameters for an external endpoint, including the user credentials an integration needs for SFTP. Launching it creates an integration event you can open in Process Monitor.
Outbound delivery is a business process step, not a side effect of the extract. The integration business process default is Initiation, then Service (Fire Integration). The file leaves Workday only if you add Service: Document Delivery after that. Inbound uses Service: Document Retrieval before Fire Integration. Configuring connectors says the delivery step needs three things: the document to send (the integration output), the transport details (URL and directory), and authentication. The same chapter says there will be three delivery attempts. It does not publish what happens after the third, or the wait between them.
Before the first real run, use Integration > Test Transport. The choices are connect only, list the directory, or send a test file. Workday says you need a success message before you launch the integration.
Studio can also open SFTP itself. The sftp-out endpoint looks like sftp://sftpserver.example.org/outputDir, and the directory has to exist already. put writes, list lists, get retrieves the first match and does not delete it, and delete is a separate method. Dual authentication defaults to false: a configured private key is used with the username and the password is ignored, unless you set dual authentication so both are required. The host key fingerprint is a separate property. Prefer the delivery service when you can. Encoding steps say Studio integrations do not have access to PGP keys stored in Workday, and that a delivery service is the better way to use those keys.
The file name the partner decrypts
Agree this in writing. Workday will not infer it.
| Piece of the contract | What Workday does |
|---|---|
| Piece of the contractThe name on the SFTP server | What Workday doesA sequence generator builds a unique name from a date, a time, a sequence, and fixed text, so the next run does not overwrite the file. If you configure one, Workday ignores the static Output Filename attribute. Studio’s output pattern can also use ${INFILE}, ${UUID}, and ${EXT}. |
| Piece of the contractThe name inside the PGP file | What Workday doesPGP filenames: the Delivery Service embeds the plaintext filename so the partner’s decrypt names the result. The .pgp name can be unrelated. If the sender embeds the wrong plaintext name, the recipient cannot deduce the right one. Workday’s own example is a file stored as ExternalStudents.pgp that arrives for processing as _CONSOLE because that was the embedded name. |
| Piece of the contractStudio encrypting without the delivery service | What Workday doesThe pgp-encrypt step has a Decrypted Filename property, which is the name embedded for later retrieval. ASCII armor, an integrity signature, and a text-mode flag are separate properties. Text mode set on data that has no line endings produces an error. |
| Piece of the contractInbound decrypt | What Workday doesRetrieval uses the embedded plaintext name. If there is none and the name ends in .pgp, Workday removes that suffix. Otherwise it may add .plaintext. |
Inbound size limits on that same business-process page: 1 GB for XML and 300 MB for XLSX. Those sentences are about document retrieval, not about an outbound payroll file. No outbound size limit was on the pages checked.
What fails after midnight
The schedule is Launch / Schedule Integration. Daily, weekly, and monthly recurrences take a time and a time zone. If the slot falls in a Workday maintenance window, Catch Up Behavior is None or Run Once. A partner who expected the file during the window will see a skip, or a single later run, and nothing else.
When the partner says the file never arrived, the business process guide tells you to open Process Monitor, then the parent event. The subsequent processes table lists the integration event and the deliver-document step separately. The extract can succeed and the delivery step can still fail on the endpoint address or the credentials. An empty file is a different miss: put a condition on Document Delivery so it runs only when the record count is greater than zero.
A chained Integration step that fails stops the parent process. That is the designed behavior. A transform that fails means the delivery step never starts. Studio completions are pickier still: Maintain Redirect treats status Failed as a failure and does not treat Completed with Errors as one. An overnight run can finish “with errors,” send a partial file, and never route the redirect you configured.
The integration system user on the service steps needs the domains the error names. A security error in the event is that gap, not a bad file layout.
Write the contract down
One page per partner is enough:
- Host, directory, and whether the directory is created by them. Studio will not create it.
- Exact file name, or the sequence pattern, and the embedded PGP plaintext name. Those are different strings.
- Which key encrypts, and that it lives in the tenant delivery service rather than inside a Studio archive.
- The run’s time zone, what a maintenance skip should do, and who is notified. Notification setup is covered in the integration inventory.
- After any sandbox refresh, retest the transport before the next night. Attribute values and per-tenant credentials are the subject of recovering after a sandbox refresh.
Kiweely Roots (coming next) treats “the files partners still want by SFTP” as a normal reach, in either direction. You describe the file, the agent builds the integration and tests it on Sandbox, and a payroll or benefits file still waits for your approval before it goes out. Register interest and name the partner file that fails overnight.