Switching pages/profiles loses timer

[mkmacd]

If you have a timer running and is showing on the button with {timer} and then you move to a different profile and back again, the timer stops showing (still runs on clockify). Would be amazing if it could keep showing.

Thanks

[eXpl0it3r]

Just a clarifying question, I assume it also doesn't start running after say 10s?

[mkmacd]

Yes that's correct.

Would also like some clarity as you're here.. I've got v1.8 which mentions about having multiple buttons. I have 28 buttons on one page (which could add to the issue...) but with minimal reliability. I'm probably pushing it, but I'm curious to understand what's going on in the background to stop it working.

[mkmacd]

More info. I think the buttons are the big issue. I've taken all the timers are put them in individual folders and having more success both with the timer reappearing and the reliability of the timers anyway. Happy to use this as a work around if there's no plan/not possible to support lots more timers :)

[eXpl0it3r]

I'm curious to understand what's going on in the background to stop it working.

Each instance will connect to the API every 10s to get the timer status. Unfortunately Clockify has quite a low-ish API rate limit. Before the previous release, I'd do it every second, which started to fail at 3+ buttons.
I've again verify the communication setup between the Stream Deck and my .NET code. Maybe I can a shared cache, that would update all the clocks in a single API call for say one workspace at a time. Then the button instances wouldn't each do API calls, but this will take some time to figure out and implement.

Currently it's recommended to have as few visible Clockify buttons as possible.