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.
Will any of the status methods work for jobs scheduled to run after the expiration time? In the readme it says "Query for job status any time later:" which makes it seem like the status will always be available. After doing some investigation, it appears that this gem works by storing a hash in redis with info about the job status and the hash ttl is the config expiration time. If this is true, I think the docs should be revised to have a clearer explanation of what the expiration time is used for as well as mentioning the impact of the expiration time on scheduled jobs in the Retrieving Status section.
Thanks
The text was updated successfully, but these errors were encountered:
Will any of the status methods work for jobs scheduled to run after the expiration time? In the readme it says "Query for job status any time later:" which makes it seem like the status will always be available. After doing some investigation, it appears that this gem works by storing a hash in redis with info about the job status and the hash ttl is the config expiration time. If this is true, I think the docs should be revised to have a clearer explanation of what the expiration time is used for as well as mentioning the impact of the expiration time on scheduled jobs in the Retrieving Status section.
Thanks
The text was updated successfully, but these errors were encountered: