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
Hi, the authors and everyone. First of all, I want to say thanks to the Quirrel author team. I am a beginner at using queues in my NextJS project. However, because of its convenience, I still want to choose Quirrel as the queue system in my SaaS application.
I have some insecure situations when using the Quirrel queue in the product environment. The question is when the application (on prod) is updated to a new version, how can I handle the pending jobs that still exist in the queue:
Job in Quirrel is a void function, so how can I know whether the job is successful?
Quirrel will continue to execute the next job when a job fails, won't it?
Will the retry mechanism at enqueue(), retry enqueue the job when the request to Quirrel API fails or when the enqueued job fails?
I need to know this information to handle Quirrel more carefully in our application.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, the authors and everyone. First of all, I want to say thanks to the Quirrel author team. I am a beginner at using queues in my NextJS project. However, because of its convenience, I still want to choose Quirrel as the queue system in my SaaS application.
I have some insecure situations when using the Quirrel queue in the product environment. The question is when the application (on prod) is updated to a new version, how can I handle the pending jobs that still exist in the queue:
I need to know this information to handle Quirrel more carefully in our application.
Thank you very much, my pals !!!
Beta Was this translation helpful? Give feedback.
All reactions