Hi Support,
I’m using a Toggle in a Chrome browser and I’m having persistant issues with time tracking. It’s fine in my mobile app, but when I track time via my browser I’m either having issues to start, or to stop. It’s only when I refresh the page (or use the mobile app) that I’m able to start/stop tracking. The browser (I’m using two different devices) doesn’t work smoothly at all, whilst I’m having no issues with the mobile app at all.
Cheers,
Ilse
I’m having the same issue. It started some time in the last 2-5 days. I’m using a chromium view within an Electron app.
Yes, that’s a great addition. It’s just recently started. There was an update last weekend, I think and it’s been happening since then.
+1
Same issue - started a few days ago. I’m using regular Chrome on Mac.
Super annoying. Please fix!!!
Exactly this. I’ve been using Toggl for years and it’s been great, but instead of complicating things and adding a bunch of extra stuff, you should focus on keeping the basics working: Start button / Stop button!
In the last few days Ive had several instances where the Stop event seems to not stick. In the UI it will show as stopped, regardless of whether I click the button or use keyboard shortcuts (c and s). Then the next morning there’ll be an email “Toggl still running”, toggl UI will not show it as running, only on browser refresh will it show as running. Seen several times in the last 3 days or so, on MacOS 15.5 with Chrome 141.0.7390.108 (Official Build) (arm64)
I was about to log it, I’m having the same issue. I stop the time, then it goes into some weird left corner, I have to stop it there, then it reappears and I have to save it again. I can’t tell if I lost time or I added too much with clients.
+1 - I’m experiencing the same issue since last week.
This is is perhaps related: Web app: Timer stops responding (can’t edit description or stop without page refresh)
Yea when I click stop it goes like this. And it doesn’t properly register the time until I refresh the page. So annoying!
Still no resolution, nor a response from Support. Can we get an update??
yepp exactly the same issue! suck 
Facing the same issue.
If my memory is correct, such bug appeared after the last server maintenance and still not fixed right now.
This bug completely disrupted the user experience on very core functionality of this app which in my opinion should be considered a P0 bug and fix as soon as possible. Not sure why this bug still there after several days…
Actually, such obvious bugs should not even appear in production since it is so obvious and should be easily found out if there is any testing
Hi there,
The team are looking into this - we’ll be in touch as soon as we know more.
Thanks
Looks like this problem is fixed for me 
Agreed, so far I’ve not seen this bug today, fingers crossed!
Seems fixed for me 
! Haven’t run into the issue in a couple days
Yes, it seems to have been fixed. I haven’t run into the issue either.
I’m having these issues now in January. Error message “Error!
pq_nextval: reached maximum value of sequence
“event_stream_sync_event_stream_id_seq”
(2147483647)”
Ceri: this has been fixed. Please refresh your browser
