Thanks for the additional info @dalli.
I currently believe that it is somewhat related to the cloud sync and the cloud sync trying to "merge" databases, which is the only place I can recall where the app currently is potentially duplicating work units without explicit user interaction. If someone is seeing this behavior without having the Cloud Sync enabled, this would be valuable information because right now I am searching specifically in the sync logic for the root cause of this problem.
I recently discovered that on Windows 11, the lifecycle events of a UWP app (which WorkingHours is) are fired in a different order than on Windows 10, which can cause the sync to not run when closing the app. I fixed this with the latest update 2.9.25. As you are both using Windows 11, @Dan & @dalli, would it be possible to download the latest update and let me know if the problem continues to exist?
In theory, the problem should still not occur if the sync fails to run when closing the app, and I will continue to investigate what could potentially cause this. @carolpharmd also mentioned that the problem occurred on a Windows 10 machine.
@dalli Can you elaborate on why it takes so many approaches to end the timer? How exactly does the app behave? And the sync icon shouldn't spin for longer than maybe 2 seconds, as this is the normal duration for the sync process (unless network problems cause the sync to slow down or fail). You should not have to manually sync before shutting down the PC.
It would also be interesting to know if the app appears to sync-(download) right after the startup on the new day, which can be identified by a reloading-animation of the work unit list.