---
title: "Which Workday Integrations May Auto-Remediate — Kiweely"
description: "How to choose which Workday integrations may apply a tested fix alone and which must wait for a person."
url: https://kiweely.com/guides/which-workday-integrations-may-auto-remediate
---

# Which Workday Integrations May Auto-Remediate

Use Workday’s approval-before-delivery pattern for payroll and benefits. Let a directory feed resume after a tested fix, and keep a person on anything that changes money or access.

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

How to decide which Workday integrations may auto-remediate

Auto-remediate means a tested fix goes into the running integration without a person approving that fix. It does not mean a failed run retries itself with the same map. Workday will not make this decision for you. Workday gives you an approval step you can place before a file is delivered, error handlers you design, and a Sandbox that is a copy of Production. [Kiweely Roots](https://kiweely.com/roots), coming next, is the product that states a default: payroll, benefits, and tax wait after a Sandbox proof on the failed rows; directory and reporting feeds resume and the owner is told; you can move any integration. Until that exists, the decision is a list you write down and enforce with the Workday controls below.

The default in this guide matches that product because the default matches the blast radius, not because a coming-next page is a control you can click.

## The Workday controls you already have

Use these as the implementation of whatever list you write. They do not classify payroll for you.

**Approval before the file exists or before it is sent.** The [integration business process guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/integration-business-process-guidelines.html) describe an outbound path with an approval step, then the service step that fires the integration and generates the file, then document delivery. Workday says this path is what you use when a person must review the data before it leaves. That is the wait rule, implemented in the tenant, for the send. It reviews a file. It does not review a new map unless you also stop and show the person what the map changed. Use the approval for payroll and benefits sends. Do not tell yourself the business process approved the repair. It approved a delivery.

**Severity, which is not a repair.** Studio’s logging course maps info to Completed, warning to Completed with warnings, error to Completed with errors, and critical to Failed. Processing continues for the first three unless your assembly skips the record. A critical message is how you stop. The course says errors should generally be brought to the launching user, and that automatic correction is part of error handling only alongside that visibility. Read that as permission to handle a known exception and a prohibition on hiding it. A global error handler, if nothing else marks the error handled, ends with the integration described as completed with errors. “Completed with errors” is not a successful remediation. It is a finished event with a problem still in it.

**Local handlers are for known failures, not for new vendor rules.** You attach them where you expect trouble: a transform, a web service, an outbound call. The course says calls to systems outside Workday fail for reasons you do not control. A handler that retries a timeout is a remediation of transport. A handler that invents a benefits code is not a handler. It is a data change, and it belongs in the wait list with a Sandbox rerun.

**Sandbox before Production.** Workday recommends deploying and testing custom Studio integrations in Preview Sandbox before Production. The tenant datasheet describes Sandbox as a weekly copy of Production and Sandbox Preview as a twice-yearly refresh that sees new functionality first. A fix that has not run on Sandbox has not met the minimum Workday already asks of a Studio change. Auto-remediation that skips Sandbox is below that minimum. Do not automate it.

**Transport success is not content success.** The connector course tells you to test the transport: connect, list the directory, or send a test file, and require a success message before launch. The benefits testing chapter then makes you run a second cycle for file format, because a delivered file can still have blank required fields and codes the provider will reject. Any auto-remediation policy that treats delivery as “fixed” will resend bad rows. The companion guide [delivered versus rejected](https://kiweely.com/guides/workday-file-delivered-carrier-rejected-rows) is that cycle in operational language.

## The decision

Score the integration. Any “wait” answer in the left column waits, no matter how many “resume” answers sit beside it.

| If this is true, a person approves the fix | If this is true, a tested fix may resume and notify |
| --- | --- |
| A wrong row can change pay, coverage, a deduction, or a tax filing. | A wrong row cannot. Reclassify reports that contain pay; the word “report” does not make them safe. |
| The consumer is a benefits carrier or a payroll provider, and acceptance is their companion guide or their acknowledgment. | The consumer is a directory or a dashboard, and the owner can tolerate a corrected record after the fact. |
| The repair changes data, not only transport. New element, new code, new population. | The repair is a retry of a timeout or a rate limit, and the payload is unchanged. |
| You cannot state the before and after on a small, named population. | You can: these rows failed for this reason; Sandbox now shows the corrected outcome. |
| You cannot put the previous behavior back quickly. | The previous version can be restored by the owner or the on-call role without a project. |
| The feed can grant or keep access. A missed leaver, a privilege attribute, a full-population replace of a directory. | The attribute is a profile field, the population is the failed rows, and a bad value is reversible. |

Payroll, benefits, and tax land in the left column on the first row almost every time. That is why a product default of “wait” is the right default and why your list should say the same even if you never use that product. Directory feeds land on the right only after you have walked the access row and the rollback row. A joiner feed that also assigns application privileges is a left-column integration with a directory name.

Reporting is not automatically the right column. Workday’s Data Cloud materials are the reminder that a report can be compensation history. If the integration’s output contains pay and a person outside payroll will act on it, wait. If it is a headcount figure for a dashboard and the correction is visible to the owner the same day, resume-and-notify is reasonable.

## What may be automatic even on a wait-listed integration

Waiting for a map change does not mean waiting for a retry of the same file after a transport failure.

| Event | Wait-listed integration | Resume-listed integration |
| --- | --- | --- |
| Delivery step failed, file never left, payload unchanged | Retry the delivery. Alert if the retry fails. Do not regenerate with a new map. | Same. |
| Vendor rejected rows for content | Do not resend. Reproduce those rows on Sandbox, show the before and after, wait. | Same reproduce-and-show. You may then resume if the integration is still in the right column after the change. Content changes are how a directory feed becomes a wait feed for one release. |
| Workday event Failed or Completed with errors, cause unknown | Stop. A person reads the messages. Studio’s course wants that visibility. | Stop. Unknown cause is not a resume. |
| Known message, handler already tested for that message | The handler may run. It was the remediation you approved when you deployed it. | Same. |
| A new field the vendor started requiring | Wait. This is a new map. | Wait for this change if you cannot diff it. Otherwise Sandbox, resume, note, and the ability to reverse. |

The handler row is the one teams get wrong. A handler shipped last quarter is an approved remediation for the exception it names. It is not a general warrant for the next exception. The Studio course’s local handler is “a particular set of issues.” Anything outside the set goes to the global handler and should stop.

## Write the list so an on-call engineer can apply it

A policy that says “use judgment for sensitive integrations” will be applied differently at 01:00 than at 10:00. Write the integrations by name into one of two lists. Review the lists when you add a feed, not when one is on fire.

For each wait-listed integration, record:

-   the business process, and whether approval is required before delivery,
-   who may approve a map change,
-   which Sandbox the failed rows are rerun on,
-   where the vendor acknowledgment is read, so “Completed” is not the only status.

For each resume-listed integration, record:

-   who is notified, on what channel, the same night,
-   the six facts the note must contain: integration, population, before, change, after, and confirmation of what has not yet been undone,
-   the restore action, and a time by which an unhappy owner can invoke it,
-   the condition that moves this integration to the wait list without a meeting. A privilege field, a full replace, or a payload that now includes pay are good conditions.

Workday’s weekly Sandbox refresh belongs in both procedures. A proof run on Friday may be a proof against a tenant that was refreshed and lost a Sandbox-only credential. The eSignature best-practice page is the published example of credentials that must be reconfigured after refresh and that must not be the production credential. If your reproduce step depends on Sandbox, check the refresh calendar before you call the proof current.

## What not to automate

Do not auto-remediate from the text of an error alone. Studio tells you a good message includes context and condition. It also tells you not to dump the raw payload into the event. A repair that parses a message and edits a map without a Sandbox rerun of the named workers is guessing.

Do not auto-remediate a Cloud Connect template by wrapping it in a second transform you do not test. If the template matches the carrier, Workday says it maintains that template when the endpoint’s requirements change. An automatic local “fix” can fight the next template update. Prefer a tested change you can point at, or a ticket to the template, over a silent override.

Do not auto-approve because a chat assistant said the file looked fine. An assistant can read a count. It cannot be the approver for payroll. The wait list is a person, in a channel that is not the model’s reply. Roots’ own page, when you evaluate it, says the payroll change waits even if an assistant requested the change. Hold your manual process to that bar now.

Do not treat Preview and Sandbox as interchangeable. Preview is for upcoming Workday behavior. The weekly Sandbox is the closer copy for “last night’s rows.” Using Preview for a vendor-format fix does not satisfy “real, current data” if Preview is months from the last refresh.

## A one-page rule you can adopt

1.  Name the integration.
2.  If a wrong row changes pay, coverage, tax, or access, it waits. A person approves. Sandbox first, on the failed rows, with a before and after.
3.  If it is a directory or reporting feed and a wrong row does not do those things, it may resume after the same Sandbox proof, and the owner is told. Rollback has to be real.
4.  Transport retries of an unchanged payload are allowed on both lists.
5.  Unknown failures stop on both lists.
6.  Move an integration between the lists in writing, when the data it carries changes, not in the incident channel.

[Kiweely Roots](https://kiweely.com/roots) is coming next and is worth evaluating against this page: per-integration switch, Sandbox on the failed rows, wait for payroll and benefits and tax, note for directory and reporting, diff, one step back. If the product resumes a wait-listed feed, it does not match its own page. If your runbook resumes one, it does not match this guide.

The lists are the control. The tools above are how you enforce them in Workday before any outside platform is switched on.

## Sources checked

-   [Integration business process guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/integration-business-process-guidelines.html)
-   [Studio logging and error handling](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-studio/logging-and-error-handling.html)
-   [Concept: Studio error handler components](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/error-handler-components/egj1510323126986.html)
-   [Test benefits connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/test-benefits-connectors.html)
-   [Setup Considerations: Workday Studio](https://doc.workday.com/admin-guide/en-us/workday-studio/setup-considerations--workday-studio.html)
-   [Workday tenants datasheet](https://www.workday.com/content/dam/web/en-us/documents/datasheets/workday-tenants-datasheet.pdf)
-   [Configuring connectors and document delivery](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/configuring-connectors.html)

## Related guides

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

-   [### Why a Delivered Workday File Was Still Rejected Workday can mark a file generated and delivered while the carrier’s companion guide still rejects segments, codes, or coverage. Those are different tests.](https://kiweely.com/guides/workday-file-delivered-carrier-rejected-rows)

### More guides on Integrations and APIs

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

-   [An Integration Run Book Assistants Can Query](https://kiweely.com/guides/workday-integration-run-book-for-assistants)
-   [When Workday Integrations Should Leave the Tenant](https://kiweely.com/guides/when-workday-integrations-leave-the-tenant)
-   [Workday API Rate Limits When Many Employees Ask Questions in Chat](https://kiweely.com/guides/workday-rate-limits-when-employees-ask-in-chat)
-   [Workday SFTP File Contracts, PGP, and Overnight Failures](https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures)
-   [Recover Workday Integration Attributes After a Sandbox Refresh](https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes)
-   [Inventory Every Workday Integration System, Schedule, and Owner](https://kiweely.com/guides/inventory-workday-integration-systems-schedules-owners)
-   [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)

### From the blog on Integrations and APIs

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

-   [Does Workday Data Cloud Kill Outbound RaaS and Studio Extracts? A Consultant’s Reality Check](https://kiweely.com/blog/workday-data-cloud-live-data-query-for-consultants)
-   [I Used to Spend My Afternoon on One EIB File. Now I Hand It to Kiweely.](https://kiweely.com/blog/messy-spreadsheet-eib)
-   [How to Reconcile Workday Payroll Feeds in Studio Without Days of Manual XML Diffs](https://kiweely.com/blog/reconciling-workday-payroll-studio-feeds-with-ai)

## 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.
