Time Tracking

Track Time During Connection Problems

Keep an active desktop session safe through a temporary connection problem and allow delayed activity and screenshots to synchronize.

Can ZMorning keep tracking if the connection drops?

Yes, if tracking was already running. The desktop app can keep its timer active and hold new minute activity and captured screenshots locally until it can send them. Starting a new session is different: Start must first retrieve the selected employer's current tracking settings, so connect before beginning a new session.

Know the boundary before working offline

Session already running

Tracking can continue

The local timer remains active. New minute activity and any scheduled screenshots enter a pending queue when upload attempts fail.

Session not started

Connect before Start

Start requests the employer's tracking settings. Without a successful response, ZMorning does not begin the new session.

Continue an active session through a connection problem

  1. 1

    Confirm the timer is still running

    Restore the desktop window or open its tray menu. A running timer or an enabled Stop Tracking command shows that the session remains active.

  2. 2

    Keep the app open

    ZMorning records each new activity minute locally and queues scheduled screenshots when their upload cannot complete.

  3. 3

    Use Stop at the real work boundary

    Connection loss does not replace Stop. End the session when the work ends, even if the connection has not returned.

  4. 4

    Reconnect before quitting

    When possible, restore the connection and leave ZMorning open so its pending records can retry.

Let delayed records synchronize after reconnecting

ZMorning retries pending tracking automatically; there is no manual Sync button.

Connection returnsImmediate retry request

The desktop window detects that the computer is online and asks the pending queue to run.

App remains openPeriodic attempts

The desktop process also retries the queue at regular intervals while it is running.

Stop or resumeAdditional retry points

Stopping a session and resuming the computer each request another queue attempt.

  1. Restore a stable internet connection.
  2. Keep ZMorning open and signed in.
  3. Select Stop Tracking if the work session has ended.
  4. Allow time for delayed minute activity and screenshots to upload.
  5. Review the relevant day before quitting or signing out.

Choose the right action while records are pending

Close the window

Retries can continue

Close hides ZMorning in the tray. The desktop process, active timer, and periodic queue attempts can continue.

Stop Tracking

Ends work and retries

Stop ends the active session and immediately requests another pending-queue attempt.

Quit

Pauses retry attempts

Pending data remains stored for a later app launch, but no more attempts occur while ZMorning is closed.

Distinguish connection loss from computer sleep

A running computer without internet access can continue producing local tracking records. A suspended computer is different: its timers and capture work do not keep running normally. When the computer resumes, ZMorning requests a queue retry, but it does not reconstruct the full time spent asleep.

Verify records without a sync indicator

The current desktop app does not show how many records are pending or announce that synchronization is complete. After reconnecting, leave the app open, then review the relevant day for the expected time, activity, and screenshots. Delayed screenshots can make the worklog refresh as they arrive.

Troubleshoot connection-related tracking

Start does nothing while offline
Reconnect first. Start needs the selected employer's current tracking settings before the session can begin.
The timer continued, but the latest work is not visible
Keep ZMorning open after reconnecting and allow retry attempts to run. Review the relevant day again after the delayed records have had time to arrive.
Screenshots appear later than activity
Minute activity and screenshots use separate pending queues and upload requests, so they do not necessarily become visible at the same moment.
ZMorning was quit before the connection returned
Open the app again when connected and remain signed in. The locally stored queue can retry after launch.
The app asks me to sign in again
Sign in while connected so ZMorning can authenticate later upload attempts, then leave the app open for synchronization.
The computer slept during the session
Do not expect the whole suspended period to appear as tracked work. Review the resulting records and start a new session when appropriate.