Unexpected? behaviour dispatching to queues.

[laravel]

Unexpected? behaviour dispatching to queues.

[gabrielalack]

I feel like there should be a warning about this on the doc page for queues. Would have saved me some time before having to come looking for this!

[taylorotwell]

Yeah dispatch the job using Bus::dispatch or Queue::push

[simik-ru]

@mattbucci

@robclancy I find the approach
App\Jobs\SendTasksDigest::dispatch(App\User::find(5))->__destruct();
causes the job to be dispatched twice

Try the following instread:

app(\Illuminate\Contracts\Bus\Dispatcher::class)->dispatch(new \App\Jobs\MyJob());

[robclancy]

For people coming here you can just destruct the object you get.

App\Jobs\SendTasksDigest::dispatch(App\User::find(5))->__destruct();

[GrahamCampbell]

This is because of the dispatch helper using garbage collection to dispatch. Call Bus::dispatch() instead to avoid this.

[mattbucci]

@robclancy I find the approach
App\Jobs\SendTasksDigest::dispatch(App\User::find(5))->__destruct();
causes the job to be dispatched twice

[GrahamCampbell]

(or whatever the name of the facade is, if one exists, you know what I mean)

[matthewhaworth]

I've just come across this, wasted many hours getting quite confused!

Is there any more info on why this is happening? We encountered it was well and were wondering about how the dispatcher is interacting with garbage collection. Just curious mainly.

[louisitvn]

This is because of the dispatch helper using garbage collection to dispatch. Call Bus::dispatch() instead to avoid this.

Can anyone explain why it was intended like that? It is really annoying.