suddenly have issues using your timer in JIRA via Firefox & Chrome. Timer stops after 31 seconds every time. Everything was fine just yesterday. Are you experiencing server downange?


Couldn't reproduce, original tweet was removed so closing for now.
Awaiting more info but a similar case, will reopen if confirmed https://app.intercom.io/a/apps/ayixs927/conversations/21189600004
@shantanuraj Looks like there is a problem
Probably related to https://github.com/toggl/toggl-button/issues/1339
Support Cases from #1339
:tada: This issue has been resolved in version 1.23.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Still getting some reports of the problem persisting after the update,
Twitter ref 1108339093606404096
"The issue persists, also with 1.23.3. And "Stop automatically at the end of the day" is disabled."
We're monitoring at this stage. @nicktoggl please keep us updated if consistent reports come in.
"The issue persists, also with 1.23.3. And "Stop automatically at the end of the day" is disabled."
That was me (didn't know Toggl was on GitHub). I avoided using Toggl Button in the past few days but will try again and update here if I have further issues. Thanks!
Just happened again. The "Time is up! Take a break" notification popped up at the same time so the Pomodoro Timer might be the culprit. Disabled it to see if the bug happens without. I'm on version 1.24.1 in Chrome 72.0.3626.121.
Hey @vweevers
I just verified the extension (1.24.1) it seems to work fine.
Are your time entries still getting stopped with the "Stop tracking..." disabled under Pomdoro settings

If you have Pomodoro mode enabled and "Stop tracking..." disabled, you'll get the
"Time is up! Take a break" notification but the time-entry should not stop.
@shantanuraj Oh that makes sense! Was this "Stop tracking..." feature recently introduced? If so, the default should probably be false? Because I didn't change any setting before the "bug" (which I now realize is a feature) started happening.
Testing now with these recommended settings.
@vweevers yeah true doesn't seem to be the right default but it's been this way for quite a while
It might have been a side-effect of a recent settings revamp we did.
I'll discuss it with the team to switch the default
Thanks for pointing it out 馃檱
On discussing it with the team, we've decided to keep the default for now,
and change it if we get more complaints on our support channel.
Closing this for now