Why Timer Entries May Appear Incorrect

If your timer in Firm360 is showing incorrect time, even though your computer’s date and time are correct, the issue is often related to your browser settings, not your system clock.

Overview

Firm360 relies on your browser to determine time settings. If your browser’s time zone or configuration is not aligned with your system, timer entries may appear incorrect.

Common Cause

The most common cause is your browser using:

  • An incorrect time zone setting
  • Cached or outdated session data

This can affect how timer start, stop, and total time are recorded or displayed.

How to Resolve

1. Check Your Computer Settings

Ensure your device’s date, time, and time zone are correct.

2. Refresh Your Browser Session

  • Log out of Firm360
  • Close your browser completely
  • Reopen the browser and log back in

3. Browser-Specific Steps

Google Chrome

  • Chrome uses your system time settings
  • If issues persist, clear cache and restart the browser

Microsoft Edge

  1. Open Settings
  2. Check for any updates and run necessary updates
  3. Navigate to Reset Settings
  4. Click "Restore settings to their default values"
  5. Clear cache
  6. Restart the browser

If the issue still persists, try turning Location on in Settings > Privacy > Location > in the right pane, click Change button and see if that would sort the issue.

Mozilla Firefox

If you are using Mozilla Firefox, it is set to UTC time as a standard so it reports UTC time to all websites. This can cause an issue with setting the wrong hours for the time tracking timer in Firm360.

Option 1:

  • Uninstall/Re-install Mozilla Firefox browser

Option 2:

  1. In the address bar, type: about:config
  2. Search for: privacy.resistFingerprinting
  3. If set to true, change it to false
  4. Restart Firefox

This setting can cause Firefox to use a generic time zone, which may impact timer accuracy.

Important Notes

  • Timer accuracy depends on browser and session settings, not just your device clock
  • Changes may require a full browser restart to take effect
  • If the issue continues, contact support for further assistance

 

Share this

Was this article helpful?

0 out of 0 found this helpful