You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like process_job is immediately run as soon as an item is inserted into the queue? So instead of queueing items and limiting their triggers, they're just being called immediately?
The worker, in my understanding, should be used when running process_job. Currently, it's used when collecting the response of process_job, in process_current_jobs_if_unlocked, which doesn't make sense to me.
Let me know if I'm missing something here. Thanks.
The text was updated successfully, but these errors were encountered:
It looks like
process_job
is immediately run as soon as an item is inserted into the queue? So instead of queueing items and limiting their triggers, they're just being called immediately?The
worker
, in my understanding, should be used when runningprocess_job
. Currently, it's used when collecting the response ofprocess_job
, inprocess_current_jobs_if_unlocked
, which doesn't make sense to me.Let me know if I'm missing something here. Thanks.
The text was updated successfully, but these errors were encountered: