---
title: "Workday SFTP File Contracts, PGP, and Overnight Failures"
description: "File names, PGP plaintext names, and the Workday delivery failures that show up after midnight."
url: https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures
---

# Workday SFTP File Contracts, PGP, and Overnight Failures

Partners still collect a named file over SFTP. Workday’s delivery service, sequence generators, and PGP filename rules decide whether that file is the one they can decrypt at 2 a.m.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   5 min read
-   Published November 16
-   By Kiweely

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](https://kiweely.com/guides/workday-integration-sftp-pgp-ssh-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](https://doc.workday.com/admin-guide/en-us/workday-studio/studio-fundamentals/uxa1532597056528.html) 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](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/integration-business-process-guidelines.html) 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](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/configuring-connectors.html) 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](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/assembly-transports/zxl1508756099410.html) 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](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/encoding-steps/pbn1509468624149.html) 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 |
| --- | --- |
| The name on the SFTP server | A [sequence generator](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/configuring-connectors.html) 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}`. |
| The name inside the PGP file |  [PGP filenames](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/encoding-steps/yad1666015910812.html): 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. |
| Studio encrypting without the delivery service | The [pgp-encrypt](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/encoding-steps/ojr1509546664817.html) 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. |
| Inbound decrypt | Retrieval 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](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/configuring-connectors.html). 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](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/integration-business-process-guidelines.html) 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](https://kiweely.com/guides/inventory-workday-integration-systems-schedules-owners).
-   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](https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes).

[Kiweely Roots](https://kiweely.com/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.

## Sources checked

-   [Concept: Integration Systems and Events](https://doc.workday.com/admin-guide/en-us/workday-studio/studio-fundamentals/uxa1532597056528.html)
-   [Configuring Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/configuring-connectors.html)
-   [Integration Business Process Guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/integration-business-process-guidelines.html)
-   [Reference: SFTP-Out Transport Properties](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/assembly-transports/zxl1508756099410.html)
-   [Concept: PGP Filenames](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/encoding-steps/yad1666015910812.html)
-   [Concept: Encoding Steps](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/encoding-steps/pbn1509468624149.html)
-   [Reference: PGP-Encrypt Step Properties](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/encoding-steps/ojr1509546664817.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Recover Workday Integration Attributes After a Sandbox Refresh Workday refreshes Sandbox and Sandbox Preview from Production every week. App attributes are per environment, refresh tokens are per tenant, and Workday does not publish a field list for classic integration attributes.](https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes)
-   [### Inventory Every Workday Integration System, Schedule, and Owner Workday represents every integration as an integration system, with a schedule, a business process, an integration system user, and notifications. There is no single owner field. This is the inventory to take from those tasks.](https://kiweely.com/guides/inventory-workday-integration-systems-schedules-owners)
-   [### Workday Integration SFTP, PGP Encryption, and SSH Key Rotation Errors Configure SFTP document delivery and retrieval, SSH key pair authentication, X.509 certificates, and PGP encryption or decryption in Workday integrations. Troubleshoot Restricted To environment mismatches, \_CONSOLE PGP filenames, and SSH host key fingerprint failures.](https://kiweely.com/guides/workday-integration-sftp-pgp-ssh-errors)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [Sandbox Checklist Before AI Chat, Custom Screens, or Integration Platforms](https://kiweely.com/guides/sandbox-checklist-before-ai-chat-screens-or-integrations)
-   [Security Review Packet: Pass-Through UI, AI Chat, and Zero-Retention Integrations](https://kiweely.com/guides/security-review-packet-pass-through-ui-chat-and-integrations)
-   [What Is an EIB in Workday? How to Build, Template and Load One](https://kiweely.com/guides/what-is-an-eib-in-workday)
-   [How do you move an acquired company into the acquirer’s Workday tenant?](https://kiweely.com/guides/workday-move-acquired-company-into-acquirer-tenant)
-   [Who can launch a specific Workday integration, and what permissions does that user need?](https://kiweely.com/guides/workday-who-can-launch-integration)
-   [Write Your First Workday Studio AUnit Tests Before Changing the Assembly](https://kiweely.com/guides/write-first-workday-studio-aunit-tests)
-   [How a Workday Sandbox Refresh Affects Registered API Clients and Redirect URLs](https://kiweely.com/guides/workday-api-client-disabled-tenants-sandbox-refresh-impacts)
-   [Register API Client vs. Register API Client for Integrations in Workday](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [Why Shared Integration System Users (ISUs) Are a Security Risk for Employee AI Chatbots](https://kiweely.com/blog/why-integration-system-users-are-dangerous-for-workday-ai)
-   [Mapping Microsoft Teams, Slack, DingTalk, and Lark Identities to Workday Worker OAuth](https://kiweely.com/blog/mapping-teams-slack-lark-sso-identities-to-workday-workers)
-   [How Workday’s Twice-Yearly Releases Break In-House MCP Servers and REST Integrations](https://kiweely.com/blog/how-workday-twice-yearly-releases-break-custom-mcp-servers)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
