---
title: "Recover Workday Integration Attributes After a Sandbox…"
description: "Sandbox and Sandbox Preview refresh from Production every week. Here is what Workday documents, and how to recover."
url: https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes
---

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

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

Monday’s sandbox is not Friday’s sandbox. Workday’s [integration app lifecycle](https://developer.workday.com/documentation/GUID-ff44b82e-ff86-46d5-aeab-7a694bd8a974/ConceptIntegrationAppLifecycle) says Sandbox and Sandbox Preview tenants are refreshed every week with production data, and it calls that out as the reason to promote and retest. The [Orchestration Builder course](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-orchestrate/orchestration-builder-core-concepts.html) says the same thing about Sandbox. After that refresh, people go looking for the SFTP endpoint, the attribute, and the credential that used to point at the test partner. This guide is how to put those back without opening Production to guess.

## What Workday documents, and what it does not

These sentences are on Workday’s pages. The last row is the gap.

| Fact | Page |
| --- | --- |
| Sandbox and Sandbox Preview are refreshed every week with production data | Integration app lifecycle; Orchestration Builder |
| A weekly refresh from Production to Implementation Preview and Sandbox Preview is the example Workday uses for notification restrictions |  [Edit Tenant Setup - Notifications](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/wil1451433814625.html) |
| An integration app attribute with a blank Environment applies to every environment. You cannot transfer attribute values across environments. Assign them in each environment |  [Assign Integration App Attribute Values](https://developer.workday.com/documentation/GUID-fa77cf35-9c39-4c02-b463-8acf1cd9a0d3/AssignIntegrationAppAttributeValues) |
| Refresh tokens in the external client credential store must exist in both Sandbox and Sandbox Preview. A token that exists only in Sandbox does not open business objects in Sandbox Preview, and Workday reports HTTP 500 | Integration app lifecycle |
| Notification restrictions chosen in Production can be applied to the environments that later receive a refresh from Production. Preview Only keeps a separate Sandbox Preview configuration across those refreshes. Preview Only does nothing while you are in Production | Edit Tenant Setup - Notifications |
| Strategic Sourcing’s own sandbox refresh preserves that product’s API keys, OAuth secrets, and external integration connections |  [Strategic Sourcing refresh](https://doc.workday.com/admin-guide/en-us/spend-management/strategic-sourcing/strategic-sourcing-admin-setup/tenant-management/concept--strategic-sourcing-ad-hoc-sandbox-refresh.html) |

The Strategic Sourcing page is about Strategic Sourcing. It is the wrong page to cite as proof that an HCM or payroll integration attribute survived. It is also the wrong page to cite as proof that the attribute was wiped. Workday does not, on the pages checked for this guide, publish a field-by-field list of which classic integration-system attributes are copied from Production and which stay behind. Treat that list as unknown. Recover from a record you took in the sandbox before the refresh, not from a theory about the copy.

[How an orchestration tells Production from Sandbox](https://kiweely.com/guides/workday-orchestrate-detect-production-tenant) covers the app-attribute pattern for environment detection. Use it with the steps below. Do not use a tenanted integration attribute as the way you detect the environment. Those values are tenant configuration, and a weekly copy from Production is exactly how a sandbox starts answering with a production endpoint.

## Before the refresh, in the sandbox

Take this in the sandbox that is about to be refreshed. Do not assemble it by reading Production. Production is the source of the copy. If you only know the production value, you cannot tell a correct refresh from a sandbox that is now aiming at the real partner.

For each integration system you actually test, write down:

-   The attribute names and the sandbox values, from Integration System > Configure Integration Attributes. [Workday Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/workday-connectors.html) describes an attribute as the tenanted value of a data element: a type of data, or a behavior such as whether prior values are included. Some attributes require a value before the integration will launch. Keep credentials in your own vault. The inventory can name the attribute and say where the vault entry is.
-   The delivery and retrieval URL and directory, from the business process step. Authentication material goes in the vault, next to a note of which integration it belongs to.
-   The schedule’s time zone and any environment restriction you set so the sandbox does not run against the production partner.
-   For an Orchestrate app, the App Manager values whose Environment is `SANDBOX`. A blank Environment is a value for every environment, including Production. Workday’s example uses `WCPDEV`, `SANDBOX`, and `PROD` as separate rows, and it says you cannot transfer a value from one to another.

Also confirm the external client credential store has a refresh token in this tenant, and a separate one in Sandbox Preview if you use that tenant. The lifecycle page is explicit: create both, or Sandbox Preview calls fail with HTTP 500.

On notifications, do the Production setup Workday describes, so the refresh does not start emailing real employees from the preview tenant. In Production, set the environment restriction for the preview environments that receive the refresh. Use Preview Only when Sandbox and Sandbox Preview need different settings. That task is how Workday says you keep preview mail pointed at a test contact after the copy.

## After the refresh, still without opening Production

1.  Read the sandbox attribute and the delivery step. Compare them to the record you took last week. Where they differ, the sandbox now holds whatever the refresh wrote. Put the sandbox value back from your record.
2.  Do not “fix” a sandbox endpoint by copying what you see in Production. That is how a test run lands on the production partner. If your record has no sandbox value, the honest state is that you do not know it. Ask the person who owns the test partner. Do not invent it from Production.
3.  Create the refresh token again in this tenant if business-object calls fail the way the lifecycle page describes. A token observed in Production is not a token for this tenant. Workday says they are created per tenant, and they are not transferred.
4.  Re-enter `SANDBOX` app attributes in App Manager. Update App Configuration first if the attribute list changed on the Console. A value left blank will apply in every environment the next time someone edits it.
5.  Run Integration > Test Transport before the next scheduled night: connect, list, or send a test file, and wait for the success message. [The file contract](https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures) is the rest of that test. The [integration inventory](https://kiweely.com/guides/inventory-workday-integration-systems-schedules-owners) is the list of systems to walk.

What you still cannot claim, because Workday did not publish it here: which attribute types the weekly refresh always overwrites, whether a sequence generator’s last number survives, and whether a delivery password is cleared or copied. Until a Workday page says so, the recovery is the record you took, plus Test Transport, plus a new per-tenant refresh token.

[Kiweely Roots](https://kiweely.com/roots) (coming next) tests every build and every fix on Sandbox before anything reaches Production. It does not replace this Workday refresh behavior, and it does not document a way around it. If the integrations you re-enter by hand every Monday are the ones that cost you the most, say that when you register interest. Roots is coming next.

## Sources checked

-   [Concept: Integration App Lifecycle](https://developer.workday.com/documentation/GUID-ff44b82e-ff86-46d5-aeab-7a694bd8a974/ConceptIntegrationAppLifecycle)
-   [Assign Integration App Attribute Values](https://developer.workday.com/documentation/GUID-fa77cf35-9c39-4c02-b463-8acf1cd9a0d3/AssignIntegrationAppAttributeValues)
-   [Orchestration Builder Core Concepts](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-orchestrate/orchestration-builder-core-concepts.html)
-   [Reference: Edit Tenant Setup - Notifications](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/wil1451433814625.html)
-   [Concept: Strategic Sourcing Ad-Hoc Sandbox Refreshes](https://doc.workday.com/admin-guide/en-us/spend-management/strategic-sourcing/strategic-sourcing-admin-setup/tenant-management/concept--strategic-sourcing-ad-hoc-sandbox-refresh.html)
-   [Configuring Connectors](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)

-   [### 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.](https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures)
-   [### 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)
-   [### How can a Workday orchestration tell whether it is running in production or a sandbox? Don’t infer it from the tenant name. Create an app attribute such as environmentName, assign a value per environment in App Manager (WCPDEV, SANDBOX, PROD), never with a blank Environment, and read it with attrstore.stringValue so a tenant with no value stops the run.](https://kiweely.com/guides/workday-orchestrate-detect-production-tenant)

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

-   [Connecting ChatGPT Enterprise and Team to Workday Without a Shared Service Account](https://kiweely.com/blog/connect-chatgpt-enterprise-to-workday-mcp-without-isu)
-   [Same Report, Different Rows: Why a Workday Custom Report Changes Output When Enabled as RaaS](https://kiweely.com/blog/why-workday-reports-differ-between-run-and-raas)
-   [What Happens When a 50,000-Row Workday EIB Times Out Halfway Through (and How to Batch It Safely)](https://kiweely.com/blog/splitting-large-workday-inbound-eib-loads-safely)

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