quantum-core
quantum-core copied to clipboard
quantum-elixir
:watch: Cron-like job scheduler for Elixir
Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot] avatar"){kind=avatar}
I noticed that with non-existing modules or functions configured in jobs, Quantom doesn't give any errors or warnings on startup. For static jos configs, should they be checked for validity?
I've a question about how to configuring quantum to run on libcluster, my use case is try to run on `n` node and let quantum run the job only once....
I'm testing that my application adds jobs to quantum correctly based on some business restrictions and I'm using `on_exit` to remove jobs again after tests. This however is causing issues...
Document Integration with [Phoenix Telemetry Supervisor](https://hexdocs.pm/phoenix/telemetry.html#the-telemetry-supervisor) / [Phoenix Live Dashboard](https://hexdocs.pm/phoenix_live_dashboard/metrics.html).
We found our jobs not running, and it turned out our Quantum based scheduler had terminated. Our jobs are configured with `timezone: "Australia/Adelaide",` and Adelaide had daylight savings move the...
This is a follow up for #240 Jobs should have the option to configure how to handle a downtime of the scheduler. 1. `transient` jobs that do not need redo-ing...
## Description Quantum currently allows configuration via Cron Notation. This works very well for statically recurring events, but doesn't work very well for dynamic ones. If you for example want...
It would be nice if a `run_strategy` could specify an `executor`. This way different executors could be programmed, that would for example allow execution in a `PG2` group.
Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
Metadata
Owner
Metadata
:watch: Cron-like job scheduler for Elixir