async: how to specify the queue ? #229
-
|
Hello, return [
yield ActivityStub::async(fn () => [
yield ActivityStub::make(IndexBaseActivity::class, $decision),
yield ActivityStub::make(IndexVectorActivity::class, $decision),
]),
yield ActivityStub::all([
ActivityStub::make(DecisionNerArticlesActivity::class, $decision),
ActivityStub::make(DecisionNerSocietesActivity::class, $decision),
ActivityStub::make(DecisionNerAvocatsActivity::class, $decision),
])
];But it does not seem possible to indicate on which queue the async child workflow will be dispatched. It's actually dispatched on the default queue. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
It's currently not possible, sorry. To control the connection or queue you will need to use https://laravel-workflow.com/docs/features/child-workflows. This is what https://github.com/laravel-workflow/laravel-workflow/blob/master/src/ActivityStub.php#L24 does under the hood but it uses an internal "anonymous" workflow. I will think about how support could be added for your use case though. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, |
Beta Was this translation helpful? Give feedback.
-
|
Yes, they are effectively the same. |
Beta Was this translation helpful? Give feedback.
It's currently not possible, sorry. To control the connection or queue you will need to use https://laravel-workflow.com/docs/features/child-workflows. This is what https://github.com/laravel-workflow/laravel-workflow/blob/master/src/ActivityStub.php#L24 does under the hood but it uses an internal "anonymous" workflow. I will think about how support could be added for your use case though.