Skip to main content

Work offline and check pending entries

Cozibud can queue supported logging actions on the device when the network is unavailable. Account changes and every advanced action are not guaranteed offline.

  1. Keep the signed-in app open. In a browser, Cozibud also offers an offline page when it cannot load.
  2. Record a supported care event. A pending state means the server has not confirmed it.
  3. While an entry waits, Log shows Saving…, with Offline when there is no connection. Reconnect and leave Cozibud open while it synchronizes. If a save needs attention, Log shows a notice that opens Save status.
  4. Check that the pending marker clears and the event appears once in Events.
The Save status page listing one change not saved yet: a wet nappy for Robin, waiting to sync and retrying automatically when a connection is available.
Save status lists changes waiting to sync on this device and anything that needs your attention.
The Offline logging page explaining that saved baby details are being used and showing the running sleep timer and feed actions.
If the app cannot load at all, the offline page still offers the supported logging actions.

Do not repeatedly submit the same care event while its result is uncertain. If a conflict says another caregiver changed a timer or event, reload the current record and review it before editing.

Pending is not synchronized

A locally visible pending entry is not yet confirmation that another caregiver or connected assistant can see it.

Network failures retry automatically. A warning icon means a correction, conflict review, or sign-in is needed. Extra recovery actions are under More options. If pending work does not clear, preserve the entry and time and see Troubleshooting.

In Review unsaved changes, compare Saved in your household with Your unsaved change, then choose Force save or Force discard. Force save applies your edited fields over the current saved record. Force discard keeps the saved record and removes your local edit and dependent changes. A failed resolution keeps the edit available for another attempt; signing out is not needed. Force save still validates the record and cannot recreate a stopped timer or replace a different operation’s saved record.