Planes, lifts, building work, bad signal at the client's office. Time tracking can't stop because of that, and in WiseData Time it doesn't: with no connection you keep starting the timer, stopping it and logging hours as usual. What changes is that the entries are stored on your device until the internet is back — and they go up on their own when it is.
The sync indicator
At the top of the screen there's an indicator with the current state:
Everything synced — nothing pending, the normal state of the day.
X entries waiting to be sent — they're queued and will go up as soon as the connection allows. Nothing to do.
X entries stuck — the server refused them and they need your attention.
Clicking it takes you to the Pending sync screen, which also has a Sync now button for when you don't want to wait. That screen is deliberately not in the menu: on a normal day it's empty, and a permanent item would suggest a routine that doesn't exist.
While it's pending
Hours that haven't gone up yet appear in the same list on the Today tab, with a Waiting to be sent badge — not in a separate box. That's on purpose: two lists would force you to add up in your head what you worked that day, and that's exactly when a queued hour gets forgotten.
The day and week totals, however, still come only from what the server has. That's why the timesheet warns you when there are entries of yours not yet sent: the total on screen is the confirmed total, not the total with the pending ones inside.
When an entry gets stuck
Stuck means the server refused that item, and the reason is written on screen. The most common case is an hour logged into a period that was approved — and therefore frozen — while you were offline.
You have two ways out, and the screen offers both:
Fix and resend — adjust what the server refused and send it again.
Reopen the period — if the hour really was worked on that day, don't change the date. Ask whoever approves your timesheet to reopen it (or reopen it yourself, if that's you) and resend. Changing the date to "make it go through" lies about when the work happened, and that number is what becomes an invoice.
Two timers at once
If you started a timer on an offline laptop and another on the office computer, both reach the server at sync time. The older one is closed and both hours are kept, flagged with Two timers at once. Nothing is silently chosen: you review and fix whatever is wrong.
The same goes for Edited elsewhere: when you edit an hour offline that someone had already changed in the app, your change is applied and the entry is flagged for you to check.
Two things worth knowing
The queue has an owner. The hours you tracked offline are yours and only go up with your account. On a shared computer, what you left pending doesn't go up under someone else's session — it waits for you to come back.
Logging out doesn't clear the queue. It stays there, dormant, and comes back to life when you sign in again. Clearing it on logout would destroy exactly the hour that hasn't been invoiced yet.
If the device runs out of storage, the system tells you and either sends the hour straight to your account or asks you to keep the window open until it goes up. In those cases, the message says exactly what to do.
Installing the app
The app can be installed on your computer or phone straight from the browser. It opens in its own window, with no address bar, and it's the most comfortable way to keep the timer at hand all day.
Where to go next
Timer and manual entry — how hours are created.
The weekly timesheet — where the pending notice shows up.
Approving hours — why a period refuses entries.
In short: with no internet, WiseData Time keeps tracking and stores everything on the device; the indicator at the top shows what's left to send; stuck items appear under Pending sync with the reason and the options to fix or reopen the period; the queue is yours and survives logout.