First Response & Preservation Technical Explainer
Could isolation affect location, time or synchronisation records?¶
Yes.
Disconnecting a device can change the records that are created and the timestamps you later see.
That matters when reconstructing a timeline.
The important distinction
Local event time and later server receipt time may diverge after isolation. Do not force them into one timestamp.
Offline activity can be recorded later¶
Imagine a device is isolated at 14:00.
An application creates local activity at 14:12, but the device cannot synchronise.
It reconnects at 16:30.
14:00Device isolated.
14:12Local application event created.
16:30Connectivity returns.
16:31Server receives queued update.
The server event may therefore describe receipt or processing at 16:31 even though the underlying local activity happened earlier.
Other records can change too¶
Isolation may affect:
- network time;
- assisted location;
- cloud synchronisation;
- online status;
- “last seen” fields;
- queued uploads; and
- provider-side activity.
A gap in cloud history may simply reflect disconnection.
Preserve the transition on both sides¶
Before isolation, record:
- visible time;
- timezone;
- connection state;
- location indicator;
- sync status; and
- an independent reference time.
Afterwards, record:
- offline banners;
- failed or paused uploads;
- lost signal;
- application changes; and
- later reconnection.
The practical point is: isolation can create timeline artefacts. Preserve the before/after state so delayed records are not mistaken for delayed behaviour.
