Exq.enqueue_in
You're seeing just the function
enqueue_in
, go back to Exq module for more information.
Schedule a job to be enqueued at in the future given by offset in seconds.
Expected args:
pid
- PID for Exq Manager or Enqueuer to handle thisqueue
- Name of queue to useoffset
- Offset in seconds in the future to enqueueworker
- Worker module to targetargs
- Array of args to send to workeroptions
: Following job options are supportedmax_retries
(integer) - max retry countjid
(string) - user supplied jid valueunique_for
(integer) - lock expiration duration in secondsunique_token
(string) - unique lock token. By default the token is computed based on the queue, class and args.unique_until
(atom) - defaults to:success
. Supported values are:success
- unlock on job success:start
- unlock on job first execution:expiry
- unlock when the lock is expired. Depends onunique_for
value.
If Exq is running in mode: [:enqueuer]
, then you will need to use the Enqueuer
to schedule jobs, for example:
Exq.Enqueuer.enqueue_in(Exq.Enqueuer, "default", 5000, MyWorker, ["foo"])