---
title: "When Does the Workday Sandbox Refresh? Every Week — Kiweely"
description: "Weekly, as a full copy of Production. Workday's public docs give no day or hour, so ask tenant management. What it wipes and how to save work first."
url: https://kiweely.com/guides/workday-sandbox-refresh
---

# When does the Workday Sandbox refresh, and what does it wipe?

Weekly: Workday replaces the Sandbox with a full copy of Production data and configuration. Public Workday docs give no day or hour, so ask your tenant management contact. Preview refreshes twice a year, Implementation on demand.

-   **Checked** against Workday on November 19
-   Applies to **Workday tenants**
-   10 min read
-   Published September 25
-   By Kiweely

Anything you built only in the Sandbox is gone after the next refresh: test hires, calculated fields, custom reports, security changes and Extend apps installed only there. Save it first with a configuration extract or move it to an Implementation tenant, as the sections below show.

For consultants and developers whose in-flight configuration, reports, integrations or test runs get wiped by a weekly refresh, **[Kiweely Vine](https://kiweely.com/download)** is a desktop AI agent for Mac and Windows that builds, configures and re-verifies Workday work directly in the tenant you connect — and replays saved multi-role checks through Start Proxy after a refresh ([download Kiweely Vine free](https://kiweely.com/download)).

## When is a Workday Sandbox tenant refreshed?

Workday’s tenant datasheet says the Sandbox “is refreshed on a weekly basis (data and configurations) with the current data from the production tenant.” The datasheet does not say which day or hour. Neither does any other page in the public Workday documentation we checked, so a plan that depends on the exact window needs your Workday tenant management contact, not a guess.

| Tenant | Refresh | Copy of |
| --- | --- | --- |
| Sandbox | Weekly | Production |
| Sandbox Preview | Twice a year | Production, plus functionality from upcoming feature releases |
| Implementation | On demand | Production |

## How often does the Workday Sandbox refresh, and can you ask for one mid-week?

Weekly is the whole schedule for the Sandbox. Workday documents an on-demand refresh for the Implementation tenant: the datasheet describes it as refreshed “in an on-demand fashion”, and the Notifications reference tells you to “request a tenant refresh from Production to non-Production” when you want a restriction applied cleanly. That wording covers non-Production tenants in general. It does not say whether the weekly Sandbox can be refreshed outside its weekly run.

Pausing is a request, not a setting. Workday’s admin guide page on deleting custom reports points customers to a “Refresh Exemption Tenant Request” article on Workday Community, which is where a tenant is asked to be left out of a refresh; the article needs a Community sign-in, and no public page says how many weeks an exemption can cover. If work has to survive longer than a week, the documented route is an Implementation tenant, which the datasheet says allows “testing outside of the Sandbox tenants standard weekly refresh window.”

## Does the Workday Sandbox have production data?

Yes. A Sandbox is created when Production goes live and is refreshed as a copy of it. That includes real worker records, payroll results, email addresses and integration systems. The Workday course manual says the Sandbox’s data “is typically a copy of the data in the actual production tenant.”

Two consequences follow:

-   Test notifications can reach real people. Create the email or SMS restriction in Production and name the target environments in **OMS Environment Selected for Restriction** (for example `SANDBOX` and `IMPL`), so the restriction is applied when those environments receive the Production refresh. The steps are further down this page.
-   Credentials do not travel. For eSignature, Workday says it “doesn’t allow credentials that are configured in Production environments to be used in Sandbox environments”, so Adobe Sign or DocuSign has to be reconfigured in Sandbox after each weekly refresh.

## Does Workday Sandbox data disappear after a refresh?

Workday separates metadata, which it provides and you cannot change, from tenanted data: “your configuration and the data that you add to Workday.” A refresh replaces tenanted data. Whatever exists only in the Sandbox is overwritten:

-   Test hires, terminations and other records you created there.
-   Calculated fields, custom reports, business process definitions, condition rules and security changes not also in Production.
-   An Extend app installed only on the Sandbox. Workday’s Extend guide says that if you don’t install the app on Production before the Sandbox refresh, you must reinstall it on the Sandbox.

The reverse also holds. A change made in Production before the refresh arrives in the Sandbox.

## Are Workday refreshes always from Production, or can I refresh a tenant with another implementation tenant’s information?

Every refresh described in Workday’s documentation is a copy of Production into a non-Production tenant. Object Transporter’s migration paths table lists Implementation, Sandbox and Preview as sources and targets for moving configuration between each other. That is a migration of selected configuration, not a refresh, and it carries no worker or other transactional data.

Workday’s Object Transporter concept page says it “doesn’t migrate transactional or reference data.” Moving the contents of one Implementation tenant into another is therefore a configuration move plus a data load, not a refresh. The Extend lifecycle guide mentions refreshing an Implementation tenant “from a tenant” without naming which tenants are valid sources, so confirm any non-Production source with Workday before planning around it.

## How do I keep work before the Sandbox refreshes?

Workday names three tools, and which one fits depends on what you need back.

| Need | Tool | What Workday says |
| --- | --- | --- |
| Save project work for a refresh | Configuration Change Tracker, then a configuration extract | Create a package of the changes, extract it, download it until the refresh completes, and reload it into the refreshed tenant |
| Back up or reload configuration to the same tenant | Configuration Extracts | Created from a Sandbox or Implementation tenant; “save your current tenant configuration before a tenant refresh and then upload it to the same tenant after the refresh” |
| Move a build somewhere the weekly refresh does not reach | Object Transporter to an Implementation tenant | Sandbox is a valid source and Implementation a valid target |

Configuration extracts cannot be loaded into Production. Workday says to import into an Implementation or Sandbox tenant and use Object Transporter from there. None of these tools save test workers; those you replay from a script.

### Worked example

Logan McNeil spends Tuesday building a calculated field and a custom report that uses it in the Sandbox. Then the weekly refresh runs.

1.  On Tuesday evening he opens **Configuration Change Tracker**, selects his user and Tuesday’s time range, and creates a change list.
2.  He creates a configuration package from the list, then a configuration extract in Customer Central, and downloads the file.
3.  After the refresh, he checks that neither object exists in the Sandbox (it was never in Production), loads the extract, and reviews the pre-migration diff before migrating.
4.  He opens both objects and confirms the saved definitions, not just the success page.

## What else does a refresh reset?

-   SMS: after a refresh, **Default SMS Configuration** shows the Production configuration copied into the non-Production tenant. Workday says to delete it to prevent page errors and to save other notification settings.
-   Notification restrictions set only in the Sandbox are overwritten, which is why Workday says to create them in Production.
-   Private keys: Workday’s integrations guidance says PGP private keys are not migrated by Object Transporter; create them in Production, then refresh. X.509 key pairs between non-Production tenants use the **Migrate x509 Private Key Pair** task in Customer Central.

## Does a Sandbox refresh create W-2 forms, file taxes or email workers?

No. A refresh copies what Production holds; it does not run **Create W-2 Data** or **Create W-2 Forms**, file with a tax agency or vendor, or publish forms to workers. The risk is what the copied tenant can do afterwards, because it now holds real workers’ email addresses, payroll results and integration systems.

| Action | Happens during the refresh? | Can happen afterwards? |
| --- | --- | --- |
| Copy worker emails, W-2 data and integration systems from Production | Yes, that is the refresh | Not applicable |
| Send W-2 or quarterly tax files to a vendor or agency | No | Yes, if someone launches a tax-filing integration in the Sandbox |
| Publish W-2s to employee self-service | No | Yes, if someone runs **Publish US Year End Tax Documents** (or **Publish US Territory Year End Tax Documents**) |
| Email workers about tasks, payslips or year-end documents | No | Yes, unless email notifications are disabled or redirected for that environment |
| SMS notifications | No | Yes, unless an SMS restriction covers that environment |

Creating W-2s is its own sequence in Workday’s year-end steps for USA payroll: **Company W-2 Audit**, **View W-2 Errors** and **W-2 Preview**, then **Create W-2 Data**, a review of the wage and tax amounts, **Create W-2 Forms**, and optionally publishing to self-service on the dates you choose and launching an integration. None of those steps is the refresh.

### How do you stop worker emails surviving the next refresh?

Open **Edit Tenant Setup - Notifications** in **Production**, not only in the Sandbox, and add a restriction under the email or general notification restrictions:

-   **Disable All Notifications** blocks email notifications, including security authentication notifications. Workday notes that One Time Passcode emails for multifactor authentication then stop too; One Time Passcode by SMS is not affected.
-   **Redirect All Notifications to Contact** or **Redirect All Emails to Email Address** keeps notifications visible for testing without reaching workers.
-   **OMS Environment Selected for Restriction** set to **SANDBOX**, **IMPL** or both applies the restriction to those environments each time they receive a refresh from Production. Workday’s own example is a weekly refresh from Production to Implementation Preview and Sandbox Preview, with IMPL and SANDBOX selected; those values also cover the matching preview tenants.
-   **Preview Only** applies the restriction to preview tenants only, so the Sandbox and Sandbox Preview can keep different settings.

Workday warns against creating or changing a restriction in a non-Production tenant while campaigns or processes are running, because notifications in flight can reach the real recipient. Its suggested route is the one above: create the restriction in Production, then refresh. A restriction made only inside the Sandbox is overwritten by the next refresh.

Engagement Builder is a separate control: automated background processing is disabled in non-production tenants. If you enable it for one in Edit Tenant Setup - Notifications, Workday says to repeat the setting in Production, or the next refresh overwrites it.

### What to check the morning after a refresh, before year-end testing

| Check | Passes when |
| --- | --- |
| Edit Tenant Setup - Notifications | A SANDBOX restriction (and IMPL, if you use it) disables or redirects notifications |
| Scheduled Future Processes | No W-2 publish, tax-filing or carrier delivery job is due without its owner’s agreement |
| Tax-filing integration systems | Launching is stopped, or the endpoint is the vendor’s test endpoint, not production |
| Benefits and payroll connectors | Deliveries are paused or point at test endpoints |
| A low-risk notification | It is suppressed, or arrives only in the redirect mailbox |
| The people testing | Payroll and Benefits know the Sandbox holds real worker contact data |

For year-end tests in the Sandbox: [check you are on the non-production tenant](https://kiweely.com/blog/verifying-non-production-workday-tenant-urls-before-changes), use **Company W-2 Audit**, **View W-2 Errors** and **W-2 Preview** to prove balances (see [W-2 box mismatches](https://kiweely.com/guides/workday-w2-box-mismatch-adjust-tax-balances)), leave publishing to self-service out unless it is the thing under test with notifications redirected, and keep vendor transmission integrations off if anyone runs **Create W-2 Data** or **Create W-2 Forms**.

Which labels your company uses for its environments, and which vendor endpoints are production, are specific to your tenant. Check the notification types your year-end process actually sends rather than assuming one restriction covers them all.

For API clients and redirect URIs that a refresh copies or removes, see [how a Sandbox refresh affects API clients](https://kiweely.com/guides/workday-api-client-disabled-tenants-sandbox-refresh-impacts).

For the tools that move configuration, see [copying configuration between tenants](https://kiweely.com/guides/workday-configuration-between-tenants) and, for what each tenant type is for, [Workday tenant types](https://kiweely.com/guides/workday-tenant-types).

## Rebuild and re-verify after a Sandbox refresh with Kiweely Vine

Configuration extracts and Object Transporter move definitions, not test runs. **[Kiweely Vine](https://kiweely.com/download)** builds and checks calculated fields, custom reports, EIBs, Studio integrations and Extend apps in your connected tenant, and saves role-based test checks (employee, manager via Start Proxy, HR) so you can replay them after a refresh — in recorded sessions in Kiweely’s own Workday Development tenant, Vine replayed 33 saved checks across six runs on an Extend app (32 passed, 1 couldn’t be run) and built and verified a custom report from one question in 38 minutes (3 of 3 checks passed). Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month.

[Download Kiweely Vine free](https://kiweely.com/download) · [Watch Vine build and check a custom report (YouTube)](https://www.youtube.com/watch?v=6CQCmhRAtWI)

## Frequently asked questions

### How often does Workday sandbox refresh?

Weekly. Workday's tenant datasheet says the Sandbox is refreshed on a weekly basis with the current data and configuration from Production. Sandbox Preview refreshes twice a year, and an Implementation tenant refreshes on demand.

### Does the Workday sandbox have production data?

Yes. The Sandbox is a copy of Production, so it holds real worker, payroll and configuration data after every refresh. Restrict notifications and integrations before anyone tests in it.

### Does Workday sandbox data disappear after a refresh?

Anything that exists only in the Sandbox is replaced by the Production copy: test hires, calculated fields, reports, security changes and installed Extend apps. Production data and configuration come in instead.

### Can you refresh a Workday tenant with another implementation tenant's data?

Workday's documentation describes refreshes as copies of Production. To bring configuration from one Implementation or Sandbox tenant into another, use Object Transporter or a configuration extract; they move configuration, not worker data.

### Does a Sandbox refresh send W-2s to the SSA or a tax vendor?

No. The refresh copies data and configuration from Production. W-2 filing or vendor transmission happens only if someone runs Create W-2 Data, Create W-2 Forms, Publish US Year End Tax Documents or a tax-filing integration in the Sandbox afterwards.

### Why do workers still get email from the Sandbox after a refresh?

A notification restriction made only in the Sandbox is overwritten by the refresh. Create it in Production on Edit Tenant Setup - Notifications with SANDBOX or IMPL selected in OMS Environment Selected for Restriction, so it is applied on every refresh.

## Sources checked

-   [Concept: Custom Report Deletion](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/report-administration/ntt1553272790684.html)
-   [Datasheet: Workday Tenants](https://www.workday.com/content/dam/web/en-us/documents/datasheets/workday-tenants-datasheet.pdf)
-   [Workday Tenants and Tools (HCM Core for Administrators)](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/workday-tenants-and-tools.html)
-   [Reference: Edit Tenant Setup - Notifications](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/wil1451433814625.html)
-   [Reference: Migration Implementation Tools](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/reference--migration-implementation-tools.html)
-   [Concept: Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/omh1634567473070.html)
-   [Steps: Create Configuration Extracts](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-extracts/create-configuration-extracts.html)
-   [Object Transporter Migration Paths](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/reference--object-transporter-migration-paths.html)
-   [Concept: Electronic Signature Integrations Best Practices](https://doc.workday.com/admin-guide/en-us/manage-workday/user-experience/electronic-signatures/concept-esignature-integrations-best-practices.html)
-   [Promote Extend Apps Through the Lifecycle](https://developer.workday.com/documentation/ujq1579478936974)
-   [Setup Considerations: Year-End Tax Reporting (USA)](https://doc.workday.com/admin-guide/en-us/payroll/year-end-tax-reporting/year-end-tax-reporting-usa-/geo1548807652974.html)
-   [Steps: Set Up, Audit, and Print Year-End Tax Forms (USA)](https://doc.workday.com/admin-guide/en-us/payroll/year-end-tax-reporting/year-end-tax-reporting-usa-/year-end-tax-forms-usa-/dan1370796910461.html)
-   [FAQ: Year-End Tax Reporting (USA)](https://doc.workday.com/admin-guide/en-us/payroll/year-end-tax-reporting/year-end-tax-reporting-usa-/pui1489433723331.html)

## Related guides

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

-   [### How a Workday Sandbox Refresh Affects Registered API Clients and Redirect URLs A weekly Workday Sandbox refresh overwrites Sandbox with an exact copy of Production, wiping any API Client registered only in Sandbox while copying Production API Clients—along with their Client IDs, secrets, and Production callback URIs—into Sandbox.](https://kiweely.com/guides/workday-api-client-disabled-tenants-sandbox-refresh-impacts)
-   [### Why Workday W-2 Box 1, 3, or 5 Wages Don’t Match Payroll Summary (and How to Fix Them) Workday W-2 Box 1, 3, and 5 rarely match gross pay on Payroll Summary because federal taxable wages and Social Security or Medicare taxable wages use different pay component groups. Reconcile with Company W-2 Audit and View W-2 Box Configuration before posting correcting manual payments.](https://kiweely.com/guides/workday-w2-box-mismatch-adjust-tax-balances)
-   [### Workday Test Data: How to Build Realistic Data in a Sandbox or Implementation Tenant Workday has no test data generator. You get test data from a copy of Production, from loads you run yourself, or from demonstration tenants. This guide shows what survives a refresh and what does not.](https://kiweely.com/guides/workday-test-data-sandbox)
-   [### What are the types of tenant in Workday? Sandbox, Sandbox Preview, Implementation and Production compared Most Workday customers get four tenants: Production, Sandbox, Sandbox Preview and Customer Central. Implementation and demonstration tenants cost extra. Sandbox refreshes weekly from Production, Preview twice a year, Implementation on demand.](https://kiweely.com/guides/workday-tenant-types)
-   [### What is the safest way to copy Workday configuration from one tenant to another? Use Object Transporter, launched from the object or from Customer Central, and read its error check, prerequisite check and diff report before migrating. Use Configuration Change Tracker for project work and extracts only for different billing IDs.](https://kiweely.com/guides/workday-configuration-between-tenants)

### More guides on Tenants and developer accounts

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

-   [Workday Regression Testing for a Small In-House Team: What to Retest, When, and as Whom](https://kiweely.com/guides/workday-regression-testing)
-   [A Workday Tenant Upkeep Calendar: What an Admin Checks Every Week, Month, Quarter and Year](https://kiweely.com/guides/workday-tenant-upkeep-calendar)
-   [How Big Should a Workday Team Be? Team Size by Company Size, From 30 Teams’ Own Numbers](https://kiweely.com/guides/workday-team-size-by-company-size)
-   [Workday Change Control for a Small Team: Request, Sandbox Test, Approval, Production and the Audit Trail](https://kiweely.com/guides/workday-change-control-audit-trail)
-   [Automating Workday R1/R2 Release Regression Testing Across Two Tenants](https://kiweely.com/guides/workday-release-regression-testing-two-tenants)
-   [Is Kiweely free for a Workday personal developer tenant?](https://kiweely.com/guides/is-kiweely-free-personal-developer-tenant)
-   [Testing in a Workday Implementation: What’s Tested, by Whom, How Long, and What Can Be Automated](https://kiweely.com/guides/workday-implementation-testing)
-   [How Long Does a Workday Implementation Take? Workday’s Own Timelines by Scope](https://kiweely.com/guides/how-long-does-a-workday-implementation-take)

### From the blog on Tenants and developer accounts

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

-   [Multi-Brand and Franchise Screens on One Workday Tenant](https://kiweely.com/blog/multi-brand-franchise-leaf-spaces-one-workday-tenant)
-   [Vine, Nest, Bridge, Leaf, and Roots: One Workday Tenant, Five Jobs](https://kiweely.com/blog/vine-nest-bridge-leaf-and-roots-one-workday-tenant)
-   [Codex for Workday Community Answers: Verify Against the Tenant Before Advising](https://kiweely.com/blog/codex-verify-workday-community-answers-in-tenant)

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