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
Thanks for the package, I just found it and I wish I had it before. 👍
May I add an idea and can you tell me if it is plauseable at all? I was thinking of implementing a listing of the current queues and any indication of t he jobs. For example: php artisan queue:list
This would list what are the names of the queues and what connection do they use (file, DB, Redis, etc...)
php artisan queue:joblist
This could echo out some identificaion for the jobs including information only what is always existing, no matter the connection type. For example, in my case, I had a job stuck in Redis, and we had no idea to figure out how to see what kind of a job it was. Was it something from the very past, or the recently executed script, we did not know. If the above mentioned command could echo the ID and the created_at for the job, I think that could help many to identify the job itself.
Thank again and I'm looking forward to your answer 👍
The text was updated successfully, but these errors were encountered:
Hey Ilia,
Thanks for the package, I just found it and I wish I had it before. 👍
May I add an idea and can you tell me if it is plauseable at all? I was thinking of implementing a listing of the current queues and any indication of t he jobs. For example:
php artisan queue:list
This would list what are the names of the queues and what connection do they use (file, DB, Redis, etc...)
php artisan queue:joblist
This could echo out some identificaion for the jobs including information only what is always existing, no matter the connection type. For example, in my case, I had a job stuck in Redis, and we had no idea to figure out how to see what kind of a job it was. Was it something from the very past, or the recently executed script, we did not know. If the above mentioned command could echo the
ID
and thecreated_at
for the job, I think that could help many to identify the job itself.Thank again and I'm looking forward to your answer 👍
The text was updated successfully, but these errors were encountered: