James Hickey

Thanks Eric! Good find 😉

This should be fixed now (or whenever the docs build ina few min lol)

Would agree with this 👍

No, all invocables that are registered via the scheduler are all tied to the same cancellation token, which is triggered upon app shutdown. What's the scenario you're looking to do?

Thanks! That's an interesting idea. I decided to go with the polling approach just to give more control over how often batches of jobs will execute. That being said, right...

`WhenAll` would process the asynchronous I/O in concurrently, but any CPU bound work will "stall" the other Tasks from continuing their own CPU bound work. My idea would be to...

Did you call `ScheduleWithParams()` in your configuration too?

So it's not an officially a public thing (yet?), but it's possible if you really want to - check out this issue for some specifics: https://github.com/jamesmh/coravel/issues/77

Coravel has it's own scheduler.

Yes, that's isn't supported right now. Would require some work since the razor renderer isn't tied to the main DI container.