Troubleshoot Layout Editor Save Issues

---

At a glance

The Layout Editor uses a two-step persistence model: Save All commits changes to the template record; Update Layout (or Update All Layouts) pushes those changes to running shifts. Most save-related tickets fall into three buckets: a "structures failed to save" error (duplicate position names), changes that saved but do not appear on Shifts (Update Layout not pressed), or lost work after closing the editor (Save All not pressed before navigating away). This article walks through each in diagnostic order.

Before you start

1. Identify what you are actually seeing. The three common failure modes look similar at a glance but have different causes:

2. An error message appears when you press Save All.

3. Save All succeeds silently, but the Shifts screen still shows the old layout.
4. You came back to the Layout Editor later and your changes are gone.
5. Have your store number and the template name ready.
6. Confirm no other leader has been editing the same template recently. Concurrent editing is a known risk factor.
7. Estimated time: two to ten minutes depending on which cause applies.

Diagnostic sequence

Step 1: Check for the "1 structures failed to save" error

If you pressed Save All and got the error "1 structures failed to save" (or "2 structures failed to save," etc.):

This error fires when two or more positions inside the same template share the exact same name. Find the duplicate and rename one of them. Two places to check:

1. Visible positions on the layout. Scan the template for two positions with identical titles. Common duplicates: "Runner 1" and another "Runner 1" instead of "Runner 1" and "Runner 2"; or "Bagger" appearing twice when copying positions.
2. Invisible positions. Positions marked Invisible still count for the uniqueness check, but they do not show on the running Shifts screen, so duplicates here are easy to miss. Look at every section's position list in the editor, including any that appear as blank space on the visible layout.

Rename one of the duplicates, press Save All again. If the error is gone, your changes committed. Continue to Step 2 to confirm they push to the Shifts runtime.

Step 2: Check whether Update Layout has been pressed

If Save All succeeded without an error, but the Shifts screen still shows the old layout:

Save All commits changes to the template record but does not push them to running shifts. This is intentional; updating a layout mid-shift can remove a position with an assigned team member and drop them from the day, so OneClick keeps the commit step separate from the push step.

Open the shift time dropdown on the Shifts screen (the three-dot menu next to the time). You should see two options:

1. Update Layout. Pushes your template changes to the currently-viewed layout time only.
2. Update All Layouts. Pushes your template changes to every layout time using this template.

Press the option that matches your intent. If you changed a template that covers multiple active times and only some updated, use Update All Layouts to catch the rest. Refresh the browser if the change still does not appear after Update fires.

Step 3: Recover lost work after closing the editor

If you came back to the Layout Editor and your changes are gone:

Save All must be pressed before navigating away. Closing the tab, reloading the page, or switching to a different section of the app without pressing Save All loses every change made in the current session. There is no auto-save; Save All is the only commit path.

If your work is lost, there is no recovery path built into the product. Your options:

1. Reconstruct from memory or notes. If the change set was small, redo the changes and Save All this time.
2. Check Layout History for clues. If any of the changes were visible on the Shifts runtime before you tried to save, Layout History may show the state they reached. Use that as a reference.
3. Submit a support ticket. If a large change set was lost and reconstructing is impractical, support may be able to restore from a backup, but there is no guaranteed recovery.

The best prevention is to press Save All often during long edit sessions (every five to ten minutes, or after every substantive change).

Step 4: Rule out concurrent editing

If two leaders were editing the same template at roughly the same time:

The Layout Editor is a single-writer surface. When two people save concurrently, the last writer wins, but both writers can see unexpected loss. There is no merge behavior.

Confirm with other leaders whether anyone else was editing the template in the same window. If yes, your changes may have been overwritten; redo and save, then coordinate to prevent recurrence. Going forward, pick one person to make Layout Editor changes at a time, or agree on a "editing" signal in leadership chat to prevent overlap.

Step 5: Check browser and connection issues

If none of the above apply:

Occasionally, save failures are transient network or browser issues rather than data issues. Quick checks:

1. Refresh the browser and retry. If Save All was failing silently, the retry often succeeds.
2. Try a different browser. Chrome, Firefox, or Safari. Some browser extensions interfere with the editor.
3. Log out and back in. Rare, but session expiration can cause silent save failures.

Step 6: Submit a support ticket

If the error persists or your changes are repeatedly lost across attempts, submit a support ticket and include:

1. Your store number.
2. The template name.
3. A screenshot of the Layout Editor and the error message if one appeared.
4. A description of what you tried to save and what happened.
5. The results of Steps 1 through 5 above (duplicate-name check result, Update Layout attempt, whether concurrent editing was ruled out, browser used).

The more of the diagnostic path you document, the faster support can resolve the ticket.

Common gotchas

"1 structures failed to save" even though I do not see duplicates.

Check Invisible positions. They count for uniqueness but do not show on the visible Shifts layout. Open the template, click through every position (visible and invisible), and compare names. Also check for trailing spaces or case differences that look like distinct names but are actually duplicates (for example, "Runner " with a trailing space and "Runner" without). [VERIFY: whether the uniqueness check is case-sensitive and whitespace-sensitive.]

Update Layout is grayed out.

You may not have permission to update layouts, or no unsaved template changes exist to push. Confirm you pressed Save All first. If Save All succeeded but Update Layout is grayed out, check your permission; the default is Manager, Director, and Operator, but store rubrics can narrow this.

I pressed Save All and Update All Layouts, but only some active times updated.

This usually means your template is assigned to multiple active times, but the update only applied to the current time window. Re-press Update All Layouts. If the issue persists after a refresh, the sync may be lagging; wait a few minutes and check again. If it still lags, submit a support ticket.

A team member was assigned to a deleted position and has vanished from the layout.

Expected behavior. When Update Layout fires after a delete, team members assigned to the deleted position are removed from the layout for that time slot. They stay on the roster but are not placed. Reassign them manually, or reconsider whether the delete was correct.

I edited the layout last week and today it looks different.

Someone else may have edited since. Check Layout History for runtime changes on the Shifts screen. For template changes inside the Layout Editor, there is no dedicated audit trail; reconstruct from memory or review with other leaders.

I want an undo button.

No undo is offered in the current product. The closest equivalent is to remember the previous state and re-enter it manually. For complex layouts, keep a written record (screenshots or a text note) of the configuration before making large changes.

Related articles

1. Understand the Layout Editor (Reference, Core slot 21). Covers the Save All / Update Layout model in depth.
2. Customize a Layout Template (How-To, Core slot 22)
3. Manage Layout Templates (How-To, bonus)
4. Review Layout History (How-To, bonus). Useful for reconstructing what happened before a save issue.
5. Request a Permission Change (How-To, Core slot 1). Use this if Layout Editor access or Update Layout is not available and you need it.

Still stuck

If the diagnostic sequence above did not identify the cause, submit a support ticket with all the diagnostic results from Step 6 above. Support typically responds within one business day.

---

Pre-publish checklist status

1 b241ce86-581e-47eb-b062-e7a93893335f complete Seven sections filled, adapted for Troubleshooting category (Steps becomes Diagnostic Sequence).

2 772829c6-a4d0-48ae-a980-a585e1418cef complete Diagnostic sequence ordered from most common to least common cause, then escalates to support ticket.

3 f3f2e1d2-4422-4cbd-926c-29558f9c08a8 complete No em dashes, no hedge words, permission-based role references.

4 ce516d96-9e8e-4aee-a661-f178d95b782f complete No real identifying data.

5 7b060fe3-a211-439f-a2d9-1091a9b40887 incomplete UI verified against Production.

6 4fac66db-f383-4886-94c9-552eb5fb3d99 incomplete VERIFY block on uniqueness-check case-sensitivity and whitespace behavior.

7 e240381c-f3a9-4863-be70-4733528afad3 incomplete Screenshots at decision points (Step 1: error message and duplicate position example; Step 2: shift time dropdown with Update Layout and Update All Layouts; Step 3: Save All button location).

8 d80322ba-01fd-4e8b-ad17-c7cef9f5d2e2 incomplete Related article links activated.

9 380c0eb7-6db5-4b4c-941c-4dc25bb89db1 incomplete Primary search term tested (likely "layout not saving," "structures failed to save," "update layout").

10 b773f59c-9336-48be-942e-2057249c8a5b incomplete Reviewed by Jared and Kevin.

Template observation

This is the third Phase 2 Troubleshooting article using the diagnostic-sequence pattern (joining Troubleshoot a Moola Redemption Issue and Troubleshoot a Team Member Not Seeing Their Shift). The pattern (ordered steps from most common cause to escalation, plus a Common Gotchas section covering variants and edge cases) is now established across three articles and should be formalized in Template Spec v0.5 as the canonical Troubleshooting shape.

Source

Existing kb.oneclickapp.com Layout Editor article FAQs ("1 structures failed to save" error explanation, "I clicked save. Why don't I see my changes?" explanation) plus the editor-entry guidance at the top of the source article (Save All before leaving, concurrent editing warning). Browser and connection step comes from general troubleshooting patterns, not from the source.