Recover unsaved work and resolve sync conflicts
Find a missing schedule, retry a failed save, or choose which version to keep.
Last reviewed
On this page
Your schedule is missing
Made without signing in: return to the same device and browser profile. Guest schedules are saved there only. If you cleared that browser’s data, restore a JSON backup if you have one; there is no account copy to load.
Made while signed in: sign in to the same ScheduleBuilder account. A different account or the signed-out workspace will not show those cloud schedules.
Only Notes is missing: choose Planning → Notes on desktop or Schedule tools → Planning → Notes on mobile web. With Android’s bottom toolbar, open Schedule tools and choose Notes in the View section. The scratchpad starts closed on a new builder visit. Hiding it does not delete its text.
The header shows Saving
Pause editing and wait for Saved. It confirms the cloud save when signed in, or browser storage when signed out. Notes save with the schedule and show the same status. A calendar connection’s last-success status is separate: Saved does not confirm that the calendar is up to date.
The header shows Offline
You can continue editing your own already-open schedule when browser storage is available. Its recovery draft stays in this browser; another device will not have the unsaved changes.
Reconnect and keep the editor open. Saving is retried when the connection returns. Wait for Saved before relying on the cloud copy. If a version-choice prompt appears, follow the conflict instructions below.
The header shows Save failed
Signed in: check your connection, then select Save failed in the header or Retry save in Notes. The local draft is retained when browser storage is available. A successful retry shows Saved; a conflict asks you to choose a version.
Signed out: keep the tab open and allow browser storage for ScheduleBuilder, then retry from the same controls. Your latest changes may not have reached storage, and guest work has no cloud recovery copy.
Still failing: keep the tab open and export JSON if the editor is available. If editing is paused, use the recovery prompt instead. A failed save is not confirmation that the cloud copy contains your latest edits.
You see “Which version would you like to keep?”
This browser has a draft that cannot safely be saved over the current account schedules without your decision. Editing and exporting are paused while you choose. If you need to compare copies, check the saved schedules on another device first.
| Choose | Result when the action succeeds |
|---|---|
| Use cloud version | Reloads the saved account schedules. A separate local copy of the draft is kept in browser storage, not downloaded as a JSON file. |
| Overwrite cloud version | Saves the chosen browser draft to your account, replacing competing saved edits where applicable. The editor reloads the confirmed schedules before you continue. |
If the action fails, the prompt remains open. Check your connection and try the intended choice again. A failed attempt is not confirmation that your chosen version was saved.
You see “Couldn’t load your schedules”
Check your connection and select Try again. Editing resumes after the schedules load successfully. Do not import a replacement just because loading failed: a failed load does not establish that your saved schedules are gone.
The problem is on a schedule shared with you
Offline: reconnect to edit. Shared schedules become read-only; their drafts are not saved to browser storage and are cleared if access cannot be renewed within 60 seconds of the last successful check.