Partial or No Time Tracked (New or Existing Users)

Symptom: A new or existing user shows partial tracked hours, or all-zero Logged/Active/Idle hours, on some or all days, even though they were working.

Likely cause: The Flowace desktop app is not installed on every workstation the user logs into. Flowace links activity across machines using the user's login identity (for shared/hot-desk setups, their AD credentials). Any hostname without the app installed produces no session at all for that day or shift, so the user's consolidated record looks incomplete.

How to Confirm?

• Pull the Multi Computer Activity Report (or the standard activity report for non-shared setups) for the affected user over the period in question.
• Check the Hostnames Used column against the list of machines the user is known to work from.
• A day with 00:00:00 across Logged, Active, Away, and Idle Hrs, or a day missing a hostname the user should have used, points to a machine without the app installed rather than a genuine no-show.
• Cross-check against attendance or leave records first, so a real day off isn't mistaken for a deployment gap.

Resolution

• Identify every hostname the affected user has logged into (from IT records or the Hostnames Used history on days that did track correctly).
• Verify the Flowace desktop app is installed and running on each of those machines.
• Install the app on any machine where it is missing.
• Confirm the user is logging in with their individual credentials (not a shared/generic login), since Flowace can only link sessions across machines to one profile when each login is unique to that person.
• Once installed, tracking resumes going forward; past gaps on that machine cannot be recovered retroactively since no session was ever captured.

Prevention

Periodically audit app deployment across all shared workstations, especially for hot-desking or rotating-shift teams. A single machine missing the install will silently create gaps for every user who logs into it, not just one person.

Should there be any inconsistencies or concerns regarding this article, contact support@flowace.ai for prompt assistance.

Updated on: 23/09/2026