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
I tried to take a shot at this PR, but it's more complicated than I expected because job.remove removes it from a bunch of indexes and lists, so it's not as simple as just calling EXPIRE on the job's key.
To keep track of successful jobs (their payloads), it could be useful to keep the job alive for a predetermined time.
This can be accomplished very easily specifying a TTL in the REDIS hash containing job informations.
The API could be:
In such way the job informations would be available for 24 hours prior to automatic removal by REDIS
Do you think it's a valid use-case?
The text was updated successfully, but these errors were encountered: