Skip to content
This repository has been archived by the owner on Apr 1, 2023. It is now read-only.

Status not working if task runs after expiration #45

Closed
rmdydo opened this issue Nov 4, 2014 · 0 comments
Closed

Status not working if task runs after expiration #45

rmdydo opened this issue Nov 4, 2014 · 0 comments
Assignees

Comments

@rmdydo
Copy link

rmdydo commented Nov 4, 2014

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

@utgarda utgarda self-assigned this Feb 9, 2015
utgarda added a commit that referenced this issue Dec 15, 2015
Added info/notes about expiration time, fixes #45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants