Back to Blog

Engineering

Cloud syncOffline recordsConflicts

How your records stay in sync

Local saves, offline queues, server acknowledgements, and the real boundaries of editing the same record on several devices.

ISEA Team

You edit an expense on the train. Later, another device receives the change. Two things happened separately: your phone saved the edit, and the other device received the state accepted by the server.

In screens that support offline use, ISEA saves the edit on your device first. It can send the change to other devices when a connection is available.

The journey of an edit

Suppose you change a lunch expense from 32 to 35. Your phone saves the edit, shows the new amount, and adds the change to its upload queue. As long as the local data remains intact, you do not need to enter it again after a temporary disconnection or app restart.

With record sync enabled and a connection available, the device submits queued operations. The server checks ownership, format, and current state before accepting a write. Changes are then distributed to connected devices belonging to the same account, where local views update.

Saved locally, accepted by the server, and received on another device are separate states. Offline devices, network delay, and operating-system background limits can leave a gap between them.

Sending changes rather than copying everything

Changing one amount does not require uploading every journal entry and habit again. Sync tracks its progress and sends changes within your account. A device that reconnects receives what it missed.

A new device first establishes its local copy, then receives incremental updates. A synchronization checkpoint helps establish whether a device has received a particular stage of server state. A network connection alone does not establish that it is up to date.

What happens when a response is lost

The server may save an edit just before the connection drops. Without an acknowledgement, the device will submit that batch again.

ISEA identifies retries through device and request identities and retains the original result. The same request with the same content reuses its receipt; a reused identity with different content is rejected. This prevents a lost response from repeating an operation. Two expenses you deliberately create are still two separate operations.

Concurrent edits in the current app

The current app submits business records using a local-submission-priority policy. When the server accepts an operation, it uses the field values carried by that submission. A later accepted update to the same field can replace an earlier one. Acceptance order matters, rather than which device displays a later clock time.

A record's contents may include its amount, category, and note. If those are sent as one field, a later update can replace them together. Individual form inputs are not guaranteed to merge without loss.

For example, A changes the amount while B changes the note, both from an older copy. If both submit complete documents, the later accepted document may bring back the old amount. For important records, let one device finish syncing before continuing on another.

Where three-way comparison fits

The write layer also supports another policy: comparing the original value, the current server value, and the proposed value. Independent object properties can merge. Different changes to the same path produce a conflict receipt, retaining the current server record. Arrays are compared as whole values. A conflicting record edit is not partially applied.

This is a separate policy, not the current app's default upload behavior. There is also a distinct document-update channel; its presence does not mean every journal editor offers live collaborative editing.

Devices, attachments, and scope

Stable record identities connect compatible clients using the same account. Attachments transfer separately from their record references, so text can arrive before a photo. AI conversation history has its own storage and retrieval path.

To continue on another device, use a compatible client with the same account, sync enabled, and a connection. This article explains how sync works; desktop and browser client availability depends on what has been released.

Sync can distribute mistakes as well as correct edits. To preserve a point in time, read about cloud backups and recovery.