Simon Grondin

[This module](https://github.com/SGrondin/bottleneck) I made might come in handy to do just that. Cheers!

Hi, thanks for opening an issue. This is happening because the Redis Scripts are not present after the instance comes back. From the Redis docs: >Also, as already mentioned, restarting...

I've been thinking and I'm now in favor of implementing this feature. I'll need some time to test/handle all possible scenarios and race conditions. I think it's possible to design...

After doing more research on this, I've confirmed that this can be done cleanly and it won't take too much time to write this feature. There are serious side effects...

I've found a way to detect case 2. and trigger case 1. instead. 💡

>May I just suggest you add a global Bottleneck.on('connectionDropped') event to be able to trigger alerts? Totally agree, something like that is required. At the moment the majority of errors...

The plot thickens... `ioredis` already transparently reloads the scripts, which only means it will silently do the wrong thing if the server didn't shutdown cleanly. @scherbenokk if your server restarts...

Hi, Your code will use a lot less memory if you do this instead: ```js for (link of links) { limiter.schedule(getData, link); } ``` That way JS doesn't need to...

@tcbyrd Thanks for the excellent bug report. Have you positively pinpointed v2.9.0 as the beginning of the issue? Regardless, I'll have to reproduce it first. I'll have a hotfix release...

Perfect, thank you. I diffed the different versions around 2.9.0 and the most likely culprit is a function scoping change in 2.10.0. > Awesome! Let me know if I can...