Did you ever find out the answer to this? I’m scheduling something that requires multiple schedules with the same handler and I only see the last ones scheduled in the IDE. I tried [overwrite: false] but that didn’t help. Would rather not create multiple handlers to fix this (that seems like a band-aid).
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
3
Because the unschedule(scheduledHandler) method only takes the name of the Scheduled Handler Method (and not the time!), it stands to reason that Handler Method Name must be a unique key, and thus cannot be scheduled more than once.
runin accepts the overwrite: false flag even though unschedule still accepts only the handler method name and not the time. so that inference may not work.
@shadowjig using multiple runin with the overwrite: false flag should work. then from the runin method handler setup the next set of runins. if that works for you?
Makes sense now. Although the docs seem lite on details!!! Do you have an suggestions to allow multiple schedules based on user input? I have hard coded 2 handlers to address this shortcoming. But I wanted to give the user the option to setup multiple schedules all using the same handler. But if there’s no way to make this dynamic, I have to hard code a limited number of handlers.
runIn doesn’t solve my problem. I want to run the schedules at specific times, not in x minutes from now. While I could write something to manage multiple schedules in the fashion, it’s not preferable.
btw note that ST officially only allows 6 scheduled jobs at a time. they dont block creating more than 6 today but have assured us that they may do so at anytime in the future.