Skip to content
Discussion options

You must be logged in to vote

Hi all,

Thanks for the reports - this was related to slow API requests erroring the whole clock. Should now be fixed with the clock auto-updating in the next few hours. Alternatively, head to app.jetclock.io settings and force restart the clock. Will close the issue but please do re-open if the issue persists.

Olly

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by oliverrees
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants