That’s definitely a bug on our side.
When a timer is garbage collected we always call cancel on it and swallow errors for when the timer has already expired, but it looks like either the error message changed on that or I missed when implemented that check because I’m checking for "does not exist" instead of "Invalid timer ID".
Thanks for the report.