FAQ: Strategic Sourcing Ad-Hoc Sandbox Refreshes
Scope and Mapping
- Which Workday tenant does my Strategic Sourcing sandbox refresh from?
- Whichever Workday tenant it is currently mapped to (Implementation or Sandbox Preview). The 1-to-1 mapping determines the source automatically.
- Where does the Strategic Sourcing data come from?
- From your Strategic Sourcing production tenant. The Workday tenant refresh triggers the paired operation to copy your production Strategic Sourcing data into the sandbox.
- Do I need to raise a separate request for Strategic Sourcing?
- No. The Workday tenant refresh request handles both Workday and Strategic Sourcing in a single combined operation.
- Can I have more than one Strategic Sourcing sandbox?
- No. Strategic Sourcing supports a 1-to-1 relationship: one Strategic Sourcing company maps to one Workday tenant.
- Does this work with Sandbox Preview tenants?
- Yes, provided the Sandbox Preview tenant is already mapped. Select the Sandbox Preview refresh request type on the tenant request.
- Will changes made in Strategic Sourcing flow back to Workday?
- No. Data flow moves strictly from your Strategic Sourcing production tenant into the sandbox.
- Can a refresh create a new sandbox?
- No. An import always loads into an existing Strategic Sourcing sandbox.
Requesting and Scheduling
- How much notice do I need to give for a refresh?
- Refresh requests must be logged at least 24 hours in advance, unless escalated.
- When exactly will my refresh run?
- In the TAR window selected on the request. Standard windows are 2 AM, 10 AM, 6 PM, and 10 PM Pacific Time, Sunday through Thursday.
- What if I need a refresh at the weekend?
- Plan against the 24-hour lead time and TAR windows. For a refresh on Saturday at 10 AM Pacific Time, log the request no later than Friday at 10 AM Pacific Time.
- What if I miss the lead time for an upcoming event?
- The refresh will be scheduled in the next available TAR window, but it may not complete in time for your event.
- Can a refresh request be escalated?
- Yes. The 24-hour lead time can be shortened by escalation through your Workday contact for business-critical events.
During and After the Refresh
- Can I keep working while the refresh is in progress?
- The source tenant remains fully available throughout. The destination tenant and Strategic Sourcing sandbox are unavailable during the purge and import stages.
- How do I know whether the refresh succeeded?
- Status is reported at each backup and restore stage. Treat a partial success as a failure and report it before beginning testing.
- Are search results available straight away?
- No. Search indexes and caches are cleared during import and rebuilt afterwards. Allow them time to rebuild before relying on search results.
Data
- Can I refresh only the data, or only the configuration?
- No. A refresh automatically copies defined production data, preserves specific sandbox settings, and clears environment-coupled records.
- What happens to work already in the sandbox?
- Any data in copied areas is overwritten by the production copy. Sandbox-specific settings (such as SSO, subdomains, and integration credentials) are preserved.
- Does my sandbox become an exact replica of production?
- No. It combines production business data with sandbox-specific identity and integration settings, while clearing environment-coupled data.
- What happens to Workday Contract Lifecycle Management (CLM) records?
- Workday CLM records are environment-coupled and are cleared during import to prevent data divergence.
- What happens to audit and authentication logs?
- Audit and authentication logs are not copied from production. The sandbox begins new logs post-refresh.
- Will my sandbox contain live production data?
- Yes, in the copied functional areas. Handle sandbox data according to your organization's production data standards.
Users, Suppliers, and Access
- What happens to supplier records and communications?
- Supplier records are copied, but supplier access is disabled, and no email notifications are sent to suppliers or users during export or import.
- Why can't a user sign in after the refresh?
- Users imported from production for the first time are set to disabled by default to prevent unexpected access and must be enabled by an administrator.
- Are email addresses masked in the sandbox?
- No. User email addresses remain identical to production.
- What happens to my sandbox's suppressed-email list?
- The sandbox's existing supplier email logs and suppressed-email lists are preserved and not overwritten.
- Do users need to sign in again after a refresh?
- Yes. Active sessions, SSO tokens, and personal API session tokens are cleared during import.
Integrations and Credentials
- What do I need to reconnect after a refresh?
- You must reconnect third-party integrations for Evisort, Adobe Sign, and DocuSign.
- What happens to Unified Supplier Integration?
- API credentials must be regenerated after the refresh to re-establish synchronization.
- Do my API keys and OAuth secrets survive the refresh?
- Yes. Sandbox API keys, OAuth secrets, and external integration connections are preserved.
- What happens to third-party enrichment data?
- Results from Dun & Bradstreet, EcoVadis, OneTrust, and sanction screening are cleared and re-fetched from providers as needed.
Troubleshooting
- My e-signature documents are missing after the refresh. Is that a defect?
- No. E-signature agreement and document records are environment-specific and deliberately omitted. Reconnect the integration on the sandbox to resume operation.
- Nobody can sign in to the destination tenant after the refresh. What should I do?
- Verify if native Workday administrator credentials were tested on the source tenant before refresh. If no native credentials exist, contact Workday Support.
- The refresh did not run when I expected. Why?
- Check the request submission time against the 24-hour lead time and selected TAR window. Requests submitted too close to a window shift to the next available slot.
- My Strategic Sourcing integrations failed after a Workday refresh. What should I check?
- Confirm that the 1-to-1 Workday-to-Strategic Sourcing mapping is intact and that both backup and restore stages completed with success statuses.