Chapter 8 · Where Your Work Lives

When Sync Goes Wrong

Sync fails for boring reasons: a token expires, a laptop loses its network, two documents want the same filename. Storskarvia's job at that moment is to tell you which of those it is, hold your work while it lasts, and never guess. This chapter is the field guide to every state you can see and what each one asks of you.

Two journeys, two indicators

Your words take two trips, and they fail independently. Knowing which one broke tells you how worried to be.

  • Your browser to Storskarvia. The save indicator near the document title reports this one. When it reads Saved, the server has your text. Save failed, retrying and Offline, will retry mean it does not yet, and Storskarvia is still trying. Not saved means the server refused the edit and will refuse it again, which the unsaved changes section covers.
  • Storskarvia to your storage. The chip at the right of the status bar reports this one, naming the provider and the path. This trip writes the real files described in Chapter 3.

A broken second leg is uncomfortable and recoverable, because Storskarvia is still holding everything and will push the backlog the moment the connection returns. A broken first leg is the one to act on, and it announces itself loudly rather than hiding in a chip.

Cloud pushes are throttled to about one every ten seconds per document, and choosing a destination or restoring a version forces one immediately. After a save lands, Storskarvia re-reads the storage record a few seconds later, so a push that failed behind a successful save still reaches your eyes.

Every state the chip can show

ChipStateWhat it means
⚠ choose where this doc livesNo destinationYou answered "Not now" on the first save. Your work is held and autosaved, with no file of its own anywhere.
⚠ stored on Storskarvia (temporary)No destination availableNeither cloud provider is switched on and this browser cannot write to a folder on your machine, so Storskarvia's copy is the only one. Open the document in Chrome, Edge, or Brave to save it to a folder.
… saving topendingA destination is set and the first successful write has not landed yet. Normal for a few seconds after you choose one.
✓ saved tosyncedThe cloud copy matches. This is the resting state.
✗ retryingerrorThe write was attempted and did not succeed. Storskarvia keeps trying on later saves.
✗ reconnectdisconnectedThere is no usable authorisation for the provider. Nothing will reach it until you sign in again.
⚠ name already taken inoccupiedA file written by a different document already occupies that path. Storskarvia has touched neither side.
Saved on this computer …local folderThe browser holds the folder, so the mark comes from the last write it attempted. See below.

The chip is a button, and clicking it reopens the storage dialog, which is where most of these states are resolved. On a local folder that is waiting for permission, the same click asks your browser for it instead.

When Google Drive or Dropbox refuses a save

When the provider says why it turned an upload down, the bar across the top of the editor says that reason and offers what helps. In every case your work is safe on Storskarvia, and Save somewhere else points the document at a different provider or a local folder.

  • Full. Your Drive or Dropbox has no room left, and reconnecting does not change that. Manage storage opens the provider’s storage page in a new tab, where you can empty the trash, delete files you no longer need, or buy more space. The next save catches up.
  • Asked to slow down, not responding, or unreachable. The provider is limiting requests, its servers are having trouble, or Storskarvia could not reach it. Nothing needs doing: the next save tries again, and Try again sends it now.
  • Won’t let Storskarvia write to this file. The provider no longer lets Storskarvia change the file. On Google Drive, Reconnect may fix it; if the file was made by another app, save the document somewhere else instead. On Dropbox the folder is often read-only or shared with you, so save the document somewhere else.
  • Blocked by your organisation. A work or school account’s administrator has settings that stop Storskarvia writing to Drive. Ask them to allow Storskarvia.
  • Too large, or a name the provider won’t accept. Save the document somewhere else, or give it a different name or folder.
  • Couldn’t finish saving this time. Storskarvia’s own attempt ran out of tries (the file kept changing as it saved). Nothing needs doing: the next save tries again.
  • A newer copy was overwritten. An older save landed over a newer one and Storskarvia couldn’t put it back. The newer copy is in the file’s version history in Google Drive: open the file there and restore it.

Reconnect: the connection lapsed

When a provider has no working authorisation, a bar appears across the top of the editor saying that provider stopped saving your work, that your recent changes are safe on Storskarvia, and that they are not reaching the provider until you reconnect. It carries two buttons: Reconnect Dropbox or Reconnect Google Drive, which restarts the authorisation handoff and returns you to this document, and Save somewhere else, which opens the storage dialog so you can point the document at a different provider or a local folder instead.

Google Drive reaches this state in one way that surprises people. Storskarvia holds a drive.file permission, which reaches only the files Storskarvia itself created, so if the credentials behind those files change, Drive refuses a perfectly ordinary edit. Storskarvia tests the connection before deciding what to show, and says reconnect only when reconnecting is the fix. See Chapter 5.

Your Account page repeats the warning under Connected storage, for Dropbox and for Google Drive alike, with a Reconnect button and a Disconnect button beside it, so a stale connection is visible even if you have not opened the document in a while.

Retrying: the write failed

The error state means the request went out and came back wrong: a provider outage, a rejected upload, a network that dropped mid-write. The same bar as above appears across the top of the editor, because a provider that signed you out can fail this way too. If you are still signed in, there is nothing to fix by hand: keep writing and the next save retries. If it persists across a session, reconnect from the bar, or use Save somewhere else to point the document at a second destination. Files already written to the old location stay where they are.

The name is already taken

This one has a specific cause and a two-click fix. Every new document is created as Untitled, so if you make several before naming them, they propose the same cloud path. When a document that has never synced is pointed at a path where a .skarvia.json already exists, Storskarvia stops.

Both alternatives are destructive, which is why it does neither. Adopting the file would pour another document's text and settings into this one, and overwriting it would destroy work that belongs to something else. The push is refused, and the chip's tooltip spells out that Storskarvia has touched the file in neither direction.

The fix: open the storage button, give this document its own name or folder, and press Save here. The next save syncs normally. Naming a document before its first save avoids the situation entirely.

Folders on your own machine

Local folders are written by your browser, not by Storskarvia's servers, so the chip reports what the browser last managed. Three things it can say:

  • A tick means the last write into your folder succeeded.
  • A cross means it failed, and the bar at the top of the editor asks you to choose a folder your browser will allow. Desktop, Documents, and Downloads are refused to every website; a dedicated folder inside one is fine.
  • Click to re-authorize means the folder permission did not survive the browser restart. One click, one browser prompt, and the pending text is written out.

Filename collisions look different here. Storskarvia stamps each local .skarvia.json with the document that owns it and will not write over one belonging to another, which surfaces as the failed-write state rather than as its own status. Rename the document and it writes cleanly. Chapter 6 covers local folders in full.

When the document cannot be loaded

Most documents keep a working copy on Storskarvia. Two kinds do not: a zero-retention document, and one whose server copy was emptied after it synced. For those, opening the document means reading it from your Dropbox or Google Drive, and if that read fails, the page has nothing to show. Anything typed onto that empty page would be saved and pushed over your manuscript, so Storskarvia opens the document with editing paused instead.

The bar says Storskarvia could not load the document from your provider, that nothing on the page will be saved, and that your file there is untouched. It offers three ways out:

ButtonWhat it does
Try againReloads the page and attempts the read again. Right for an outage or a dropped network.
Reconnect Dropbox / Reconnect Google DriveSigns you in again, for when the provider signed you out. The bar also names the path where the file should be, so you can check it is still there.
Start emptyFor a file that is gone for good. It asks first, deletes nothing, and opens the document empty and editable at the same destination. If a file turns out to be there after all, the next save refuses to write over it and asks you to choose a different name.

Only the owner sees the last two, because the read uses the owner's connection. Someone reviewing a shared document is told to try again later or ask the owner to check their connection.

Edited somewhere else, and conflict backups

Because the file is genuinely yours, it can change while Storskarvia is not looking. On open, Storskarvia compares the cloud copy against what it last wrote, and adopts the cloud copy if it has moved on. If you also have edits that never synced, those are preserved first as a version named conflict backup with the date and time, so both drafts survive and you pick the winner in Versions. Restoring one is itself non-destructive, as Chapter 7 explains.

A local folder asks instead of acting: if the file there is meaningfully newer, Storskarvia asks whether to load the local copy, and answering no changes nothing.

Zero retention removes the conflict backup on purpose. That snapshot would write your entire manuscript into a new database row at the moment you were least likely to be watching, which is the thing the setting exists to prevent. On a zero-retention document, let the chip read synced before you edit the same text elsewhere.

Unsaved changes from this device

If a save never reaches the server, your browser keeps the text locally anyway, and two things follow from that.

While it is happening, a warning appears once two attempts in a row have failed, saying your work is safe on this device and has not reached the server, with a Try now button. Retries continue on their own, backing off from four seconds to a minute, so a brief outage resolves without you touching anything.

A refused save is different: the indicator reads Not saved and the warning appears at once, because no retry will change the answer. Usually the page was left open across an update or never loaded the manuscript, and the warning says to reload. A reviewer making a change their role does not allow sees the same thing, as Reviewing Someone Else’s Draft explains.

The next time you open the document, if that stored text still differs from the server's, a bar offers it back: when it was written, its word count against the server's, and a plain statement that it was never saved. Restore them saves it through the normal path and reloads; Discard throws it away. When both word counts match, the bar says so and tells you the difference is in formatting or production marks, which is the case worth reading twice before discarding.

What to do while it is broken

Keep writing. Every state on this page leaves at least one complete copy of your document somewhere, and most leave two. Sync catches up when the obstacle clears, and nothing is discarded quietly in the meantime.

If a state persists and the fix is not obvious, the ✎ Feedback button reaches the people building Storskarvia. Quote the exact chip text and name the provider, which is usually enough to identify the problem without a screenshot. The status bar itself, and everything else it carries, is the subject of A Tour of the Editor.

Updated 2026-10-16 · Full contents · Something wrong or missing?

Start writing free