Hi @scottfrazer / @gwolff
Thanks guys for sorting this out. I can confirm that, in the absence of another route, normal routing to Thingspeak works fine, even with multiple notes and rate limiting. That makes a big difference - thank you!
Manually re-routing a note still doesn’t work, but I don’t really care about that.
Hey guys, sorry to be a pain, but the rate limiting routes aren’t all getting through. Some do and some don’t. For the past few days, I’ve been trying to find a pattern, but no luck. Have a look at the routes I have been manually re-routing in the last 3 days for the routes ThingSpeak_LoRa_sat and Thingspeak_Sat.
There does appear to be something wrong on our end here… Perhaps some kind of race condition
For example I see events for a particular device being routed to Thingspeak_Sat at these times:
2025-10-08 07:14:27.508923 (success) (link)2025-10-08 07:14:27.614262 (fail) (link)2025-10-08 07:14:42.64002 (success) (link)It looks like the first and the last one are 15 seconds apart, but another one snuck in there only 100ms after the first one.
I will investigate this and get back to you
@rberkelm I think I see the bug. We’re checking the rate limit after we route, not before. So two events that come reach Notehub at the roughly the same time will both get routed and THEN we rate limit.
By the way, I’m glad you reach out with these issues, it helps us make a better product and a better experience for you. This rate limiting code is fairly new anyway so it hasn’t been hardened by lots of use yet. I’ll work on a fix and we can get it deployed as soon as possible.
I’ve just committed a fix for this rate limiting bug and it’ll go out in our next release
Hey @scottfrazer
Love your work! Thank you. Looking forward to it.
the fix was deployed. Let me know if you notice any other issues.
Works like charm! 
Thank you!