Field work

Offline

Updated 2026-11-13

Cablefolio keeps working in a plant room, a basement, or a lift: keep a property on your phone before you go, and every change you make with no signal waits in a queue and is sent, in order, when the signal returns.

Keep a property on this device

With a signal, open the property and press Keep offline. On a client's page the same button keeps every property under the client.
Wait for the "Kept offline" message. The whole property is copied, with each photo's thumbnail and each file.
The button now reads Kept offline with the date, and Refresh and Forget beside it.

Press Refresh before a visit to bring the copy up to date, and Forget when you no longer need it. Anything you opened while you had a signal can also be read again without one.

A file too large to keep is named in the list rather than silently missing.

See what this device holds

Open Settings, then Offline. Kept properties lists each one with when it was kept and its size, and Refresh and Forget for each.

Work with no signal

When the connection drops, a banner says "You’re offline. Changes are saved here and sent when you’re back."

Edit as usual. Each change shows on the page straight away and the message says "Saved offline; will sync".
What works: clients, properties, rooms, racks, and devices (add, edit, move, reorder, duplicate, delete); cable runs, one at a time or a batch from a pattern; links, power feeds, notes, contacts, checklists and their steps, VLANs, presets, photos, and files.
A photo taken with no signal shows its own picture at once, from the copy waiting to upload.
Something you create offline shows ID pending sync in place of its short ID until it reaches the server.
The label reader in Scan a code matches against the properties kept on the phone. See Labels and QR codes.

What needs a connection

These say "Could not reach the server" rather than pretend to have worked:

Signing in, your profile, security, second factor, and API tokens.
Accounts, webhooks, and share links.
Revealing a device's credentials or a property's access codes.
Importing devices from a file.
Reports, PDFs, Word documents, CSV and Excel downloads, and the map pictures.
Search across the server.

Watch the queue

While changes are waiting, a line at the top of the screen says how many ("3 changes waiting to sync"). Press it to open Settings › Offline, where Waiting to sync lists each change and what it is doing:

Waiting to send, or Waiting to try again after a dropped connection or a busy server.
Refused, with the server's own reason, when it broke a rule (a duplicate VLAN tag, for example).

The queue sends itself, oldest first, as soon as the browser is back online, and stops at the first change that does not land — so a device added to a new room never arrives before its room. Sync now sends it straight away. On a row, Try again retries it and Discard drops it.

Settle a conflict

If someone else changed the same record while your change waited, the change is held, not applied. A banner says how many conflict ("1 change conflict"); press it to open Settings › Offline.

Compare What you changed with What the server has.
Press Keep mine to send your change on top of theirs, or Take theirs to drop your change.

Nothing is decided for you: an edit made on site and the one that overtook it are both somebody's considered choice.

Signing out removes everything this device kept, including changes still waiting to sync. Send or settle them first.