Hi, I’m working in the Square Sandbox and running into a blocking issue on two related pages: Team Members and Shifts/Scheduling.
Issue 1: Cannot create a new Team Member
On the new team member creation page, the “Access” step of the new team member flow fails to load with:
“Oh no, something went wrong. It looks like we are experiencing some problems on our end.”
Failed to fetch dynamically imported module: shared-react-mfe-production-c.squarecdn.com/assets/deployed-entrypoint-lYVddMLe.js
This blocks me from creating any new team members in the sandbox.
Issue 2: Cannot access Shifts/Scheduling
On app.squareupsandbox.com/dashboard/shifts/subscribe, the Shifts Plus subscription modal shows the same red banner:
“It looks like we are experiencing some problems on our end.”
I’m unable to subscribe to Shifts Plus or access scheduling features as a result.
Troubleshooting already tried:
Hard reload (Ctrl+Shift+R)
Cleared browser cache
Tested in Incognito mode
All three attempts result in the identical error
Status check: Checked Square’s public status page - no active incident is listed for any region.
What I need: I need to create team members and set up shift schedules in this sandbox to test our Labor API and inventory integration. Is this a known sandbox issue, or is there a workaround?
@irum - This is a known limitation of the Sandbox Dashboard — it does not support the full set of production Dashboard features. Certain UI flows (like the Team Member “Access” step and the Shifts Plus subscription modal) rely on modules that aren’t available in the Sandbox environment, which causes the errors you’re seeing.
As a workaround, you can use the Square APIs directly instead of the Dashboard:
Team Members → Use the Team API (CreateTeamMember) via the API Explorer in Sandbox mode to create team members.
Shifts/Scheduling → Use the Labor API (CreateScheduledShift) to create and publish shifts. Make sure you’re on API version 2025-05-21 or newer and call PublishScheduledShift after creating — shifts are drafts until published.
Hi—same underlying Sandbox limitation, but we need clarification on a specific developer workflow.
We are developing a payroll-preparation integration with both connected and manual-import paths. We created two mock restaurant sellers in Square Sandbox. Each intentionally has exactly five team members so the production model stays within Square Shifts Free. We created genuine closed timecards through the Labor API and can retrieve them through the API.
The blocker is seller-facing export validation:
Staff → Time tracking → Timecards redirects to /dashboard/shifts/subscribe.
Workday also redirects there.
Closing the modal works, but choosing either route returns to it.
The page lists Shifts Free but only offers a Shifts Plus trial; there is no visible Free activation option.
We need Square’s native Export shifts CSV—its filename, columns, and wording—to validate a genuine manual-import workflow. Generating our own CSV through the API would not validate Square’s provider export, and we will not instruct customers to upload a report we have never inspected.
Is there a supported way to:
Enable Shifts Free for a Sandbox seller;
Expose Labor API-created timecards and the native Export shifts function in Sandbox without Plus;
Provision a non-billed developer test seller with this Dashboard capability; or
Provide a documented canonical Export shifts sample and schema if Dashboard export is impossible?
If native timecard export cannot be tested in Sandbox, please confirm that explicitly and advise the supported developer path for validating it before production.
Unfortunately, this is a limitation with Sandbox that we can’t enable on our side. The workaround that we would recommend is to create a free production-level account and continue with testing for Labor API with that account.
