Replies: 3 comments
|
Also facing this issue |
0 replies
|
also seeing this issue |
0 replies
|
The fix for us was just to add an |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi all
Just reporting an issue that may be a roadblock for others, possibly solved in docs or in code, but with Laravel Vapor the recent queue change was breaking.
It assumes "default" is a functional queue, but with vapor the queue (if unspecified) is {app_name}-{environment}.
Thank you
All reactions