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
{{ message }}
This repository has been archived by the owner on Apr 1, 2023. It is now read-only.
If you use store function in the worker and worker has no custom expiration set, the expiration will be reset to 30 minutes. If the job finishes before expiration, the correct expiration from ServerMiddleware is set and all is good. But if the job takes more than 30 minutes after store and no other status call is used, it will expire.
If you use
store
function in the worker and worker has no custom expiration set, the expiration will be reset to 30 minutes. If the job finishes before expiration, the correct expiration fromServerMiddleware
is set and all is good. But if the job takes more than 30 minutes afterstore
and no other status call is used, it will expire.It is due to implementation in
sidekiq-status/lib/sidekiq-status/worker.rb
Line 14 in 68d5c5e
The text was updated successfully, but these errors were encountered: