James Hickey

I did a quick spike on this last night, but I forgot that there are built-in events that may or may not have listeners available in the service container... which...

This isn't supported right now. Would have to be added to the codebase.

The "prevent overlap" feature only applies to jobs that are run within the scheduler. Adding a ".Once()" method to the scheduler could work. But that means having to deploy the...

Nice! I like that idea. Similar some of the stuff hangfire offers. Now that you lay out that scenario, I like the idea of a `Once()` method... The only issues...

To recap, there are two concerns here: - prevent overlapping between scheduler and queue for a single invocable - add a `Once` method to the scheduler Ex: `scheduler.EveryHour().Once();` Related, a...

@oltronix it's been a while on this issue... Curious if this is still needed? If so, wondering if using the queue instead would work. Something like `QueueIn(TimeSpan time);`? Or were...

Great, thanks for the feedback 👍

Hey, Right now you would have to use the Mutex explicitly as mentioned above. I've got another feature on the go that's similar to this one so after that one...

This is where implementing `Coravel.Invocable.ICancellableInvocable` on an invocable class can help you (see [docs for more](https://docs.coravel.net/Scheduler/#invocables)). If there's a loop, for example, where you're making API or DB requests to...

Yes, would be very helpful to see the code for the invocable / task that's causing issues :)