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
The job will be pushed with QUEUED as the id, and only the last job that will be run. That's because this line read from to use an incremented number as the job id.
I propose to use something that doesn't read from redis as the value for id, such as uniqid.
Also, can I know the reason why we used hset to store the job message and only push the job id to the list, instead of directly pushing the id along with the job message to list and not using hset?
The text was updated successfully, but these errors were encountered:
If I have code that look like this:
The job will be pushed with
QUEUED
as the id, and only the last job that will be run. That's because this line read from to use an incremented number as the job id.I propose to use something that doesn't read from redis as the value for id, such as
uniqid
.Also, can I know the reason why we used hset to store the job message and only push the job id to the list, instead of directly pushing the id along with the job message to list and not using hset?
The text was updated successfully, but these errors were encountered: