[jazzyjackson]

Hmm, settimeout is one shot, setinterval is the repeating one, unless that’s calling itself recursively?

Anyway using delays hoping that things are in place in 300ms is asking for trouble, I thought reacts whole thing was to put everything in a component lifecycle callback so everything happens in the order it needs to

[earthboundkid]

Good point! There must be some other interval causing the timer to be set.

[editkid]

Hello! Thanks for having a fossick through our code ;) Happy to report that the issue has now been resolved. I've added a post explaining the underlying cause a little up in the thread. (I'm not sure how notifications work on HN, so figured I'd drop a reply here, too).

[earthboundkid]

Awesome!