Working offline
What you can read and write without a connection, how queued changes reach Symbol, and what happens when one cannot be applied.
Symbol Bridge, the Symbol CLI and the desktop and mobile apps can keep working on your own content when Symbol cannot be reached. A change made offline is a proposal: Symbol checks it when it arrives, and you are told about anything it could not apply. The website stays online only.
Offline work covers what is already on your device and what you own. It does not make every capsule available everywhere, and the limits below are part of how it works.
Reading offline
Reads come from a local copy of your account. On the Bridge and the desktop and mobile apps you can open capsules with their fields and the summaries of what they reference, list capsules, Types, collections, projects and workspaces, search, follow references and backlinks, find orphans, and read a Type's guidance and a project's context.
Every offline answer says how old the copy is.
Cold and partial copies
A device can only answer from what it has already received.
- A cold copy has not finished its first download, so it cannot answer yet.
- A partial copy is missing some content, and says so. It shows what it has, and refuses a question it cannot answer truthfully, so a missing download never looks like an empty result or an orphan.
An old copy is still usable, with its age shown. Once Symbol tells a device your access changed or you signed out, that device stops using the copy.
Organizations that do not allow local copies
An organization can forbid local copies of its content. Its capsules are then not stored on your device and cannot be read or edited offline, and a device that learns of the rule removes what it held. Your drafts and the changes waiting to be sent are kept.
Attachments
A file opens offline only if it was already downloaded to this device. Anything else is named as unavailable. A saved link to a file is not enough, because those links expire.
Writing offline
You can create capsules, edit the title, summary, body and field values of your own capsules, and add entries to a log you own. Through Symbol Bridge you can also edit or delete those entries, and an assistant can make anchored edits. Required fields are checked on the device before anything is queued, so saving a capsule as unfinished, before its required fields are known, needs a connection. Tags and files need a connection, and so does changing an existing capsule's alias, project or visibility. A change that asks for any of these is refused whole and nothing is queued, so part of it is never saved without the rest.
A log entry added offline keeps the time you wrote it, so a daily, weekly or monthly log files it under that day, week or month even when it is sent later.
A queued change shows up in your own lists and reads, marked as not saved yet. It belongs to the account that made it: signing out keeps it, signing back in to the same account brings it back, and another account on the device never sees it.
If an assistant writes to a Type with guidance, it needs a guidance check it was given while online. Without one, the change is kept but is not sent automatically, and it needs a new read of the guidance.
What needs a connection
Sharing, access changes, publishing, Type and field changes, deleting or archiving capsules, billing and security settings all need a connection. They are refused offline with a clear message and are never queued.
When you are back online
Queued changes are sent in the order you made them, without you doing anything. A capsule you edited several times offline gains one new version for that session.
One change that cannot be applied does not hold up the others, except for changes that depend on it.
Queue states
| State | What it means |
|---|---|
| Queued | Waiting to be sent. |
| Needs guidance | Kept, but it needs a new read of the Type's guidance before it can be sent. |
| Sending | On its way to Symbol. |
| Result unknown | The answer was lost. The device asks Symbol what happened and never guesses. |
| Applied | Saved. |
| Awaiting approval | In a protected Type, waiting for a decision. |
| Refused | Not applied, with the reason. |
| Conflicted | The capsule changed elsewhere. You choose which version to keep. |
| Blocked | It depends on another change that was not applied. |
| Discarded | Dropped. |
The apps word these states in their own way, for example "Waiting to send" or "Needs your decision".
Every refusal or decision you need to make also appears in your Inbox. You can discard a change that is not already saved or being sent. Discarding cannot undo a change Symbol has already applied.
Fixing a change that was not applied
A change that was refused, blocked or discarded keeps its text and its reason. Open it as a draft to fix it: Edit draft in the Symbol app's offline changes (discarded changes are listed under Discarded on this device), or the recover commands in the Bridge and the command line. This works for new capsules, edits, and log entries added, edited or deleted.
The draft is a copy. The original change stays as it was, with its reason, so you can always see what happened. Nothing is sent until you choose Send again, which makes a new change that is checked like any other. Deleting a log entry again asks you to confirm first. For a new log entry you can also correct when it happened, or leave it empty so Symbol uses the time it takes the entry. A change can be sent again only once, and a change Symbol already applied, or one whose result is still being checked, cannot be reopened.
Symbol records which change the new one replaced, so its status and your data export show the two together.
Changes that depended on the one you fixed stay on hold until you fix them too. They are never quietly pointed at the new change.
A new capsule has its reference, such as @notes/12, set aside for it when your device first gets it ready to send. If it is then never sent, Symbol releases that reference after about seven days, and the change is refused when it does arrive. Its text is kept: reopen it with Edit draft and send it again, and it gets a new reference. A released reference is never given to another capsule.
Until it is sent, you can read a refused new capsule by its local reference on the same device and account. It is shown as a draft Symbol has not checked or approved. Nobody else can see it, and local references are never sent to Symbol.
When a capsule changed elsewhere
Symbol combines changes to different fields. If the same field changed on both sides, the saved version stays current, and your offline edit is kept as a version of its own in the capsule's history. Fields are compared whole, and a body is one field, so nothing is merged line by line.
Compare the two in the capsule's history on the website, or in the Symbol app on the device where you made the change, then choose:
- Keep mine makes your offline version the saved one. It is checked again like any other change. If the capsule has changed again since, you are asked to compare once more, and nothing is overwritten.
- Keep saved leaves the capsule as it is. Your offline version stays in the history.
Approval
An offline change to a protected Type goes into approval like any other change to it. New capsules written offline that refer to each other are reviewed and decided as one change.
Encrypted capsules
Encrypted content stays encrypted on the device, in the queue and in Symbol. A capsule written offline is encrypted before it is stored or sent.
When an encrypted capsule has a conflict, the alternative is kept as encrypted data with its own key. The website cannot read it, so it shows a placeholder. Compare and choose in the Symbol app on the device where you made the change: it needs a connection and your keys unlocked. Symbol Bridge and the CLI list the change as conflicted, and the choice is made in the app.
If your keys are locked, queued encrypted changes wait until they are unlocked. If you lose access to your keys, recovery works the same way as for any encrypted capsule, and without a key your offline text cannot be read.
In your data export
When you export your data, the file includes your offline work as Symbol received it: the outcome of every change your devices sent (applied, waiting, refused, conflicted or discarded) with its reason, the Inbox notices about those outcomes, and every alternative still kept after a conflict in your personal workspace or an organization you belong to. An encrypted alternative is included only as encrypted data. The exact bytes of a change that is still being processed are not included, since they carry the guidance checks that authorized it; your device keeps the original.
Desktop and mobile
On a computer, the desktop app and the Bridge send queued changes while they are running. The desktop app reads the local copy that the Bridge's background sync keeps, so it can answer offline once the Bridge has synced.
On a phone, the app keeps its own copy. It sends queued changes when you open it, when you return to it, and about every minute while it is open. Nothing is sent once the system has closed the app, so open Symbol to send them.