James Hickey

Thanks for reaching out! Given how coravel is implemented, I don't think something like `EveryMinuteOn()` would be that straightforward. That being said, this does seem like a "unique" case. I'd...

This is a feature I have planned to add - a distributed scheduler. Another option right now is, if you know how many instances you have (how many nodes), then...

Nice. I was thinking of taking the approach that laravel takes (which I've already pre-architected out in Coravel's code). Right now, for example, calling `PreventOverlap` internally uses a shared mutex...

Awesome. Haven't had a chance to check it out. Glad you nailed it down!

Probably not anytime soon TBH 😥 I'd like to but not a priority among life's various challenges right now 😉

Each instance will execute the schedules. So if 5 instances exist (for example), then 5 jobs will be executed in parallel.

Yes, this is something that has come up before. I'll keep this open but will most likely look at doing this as part of a major revision/piece of work 🙂

Thanks! I'm going to be away for a few weeks most likely, just FYI. Will check this out when things settle down for me 👍

Thanks again for this. I have some minor suggestions :) What if instead of returning the CancellationToken to the caller, we would add a new method on the `IQueue` like...

More on the comment above, eventually I actually think removing `QueueCancellableInvocable` might make sense. In the other queue methods, we would simply check if the invocable in question implements `ICancellableTask`....