Canceling recursively scheduled function runs
Looks like the big red button doesn't work for recursive loops that return immediately 😬
9 Replies
Hey @erquhart, we're working on fixing this!
For now you can cancel the functions by deploying to the deployment.
got it
(deploying a codebase that has the scheduled function removed)
has to be removed?
or maybe renamed
Sure, or add some logic that will stop the scheduling
ah that makes sense
way back when we first introduced the scheduler...
pulls up the creaky rocking chair
we just started counting the days until the first fork bombs and infinite loops appeared 😄
so yeah, we're working on better ways to understand and have a handle on these patterns when they get away without feeling like you've created a billing issue for yourself or something accidentally
too easy to make this mistake right now
Yeah, makes sense. Renaming is a solid recourse fwiw, temporarily (a few seconds) renaming + cancelling scheduled runs might be a decent red button approach for now.
@Emma started working on the fix today so stay tuned 🙂