Debounced jobs only working through Dispatchable::dispatch?

[osteel]

Laravel Version

13.12.0

PHP Version

8.4

Database Driver & Version

No response

Description

While testing debounced jobs, I noticed that they seemed to be processed immediately when dispatched through Illuminate\Bus\Dispatcher, and correctly delayed when using the Dispatchable::dispatch method.

Taking a closer look, I can see that the latter returns an instance of PendingDispatch (and so does the dispatch() helper), but the former doesn't. This isn't documented as far as I can tell, and I would expect Illuminate\Bus\Dispatcher::dispatch to behave in a similar way.

Steps To Reproduce

Dispatch a job using either method and observe the difference.

[scabarcas17]

Confirmed. The debounce wiring lives in PendingDispatch, so it gets skipped whenever a job doesn't go through one.

The owner token and the delay are set in PendingDispatch::acquireDebounceLock(), which runs from __destruct() right before the job is handed to the dispatcher.
dispatch() and Job::dispatch() both return a PendingDispatch, so they pick it up. Bus::dispatch() (and injecting Illuminate\Contracts\Bus\Dispatcher directly)
skips that layer and calls dispatchToQueue() straight away, so debounceOwner never gets set. With no owner, CallQueuedHandler::commandShouldBeDebounced() returns
early, and since no delay was applied either, the job just runs immediately and is never superseded.

dispatch(new ProcessThing('x'));        // debounced
Bus::dispatch(new ProcessThing('x'));   // not debounced, runs right away

ShouldBeUnique behaves the same way btw — its lock is also acquired in PendingDispatch (shouldDispatch()), same with afterCommit/afterResponse. So it's not
really debounce-specific, the lower-level Bus\Dispatcher just doesn't apply any of the "pending" behaviour. Either worth a note in the docs, or moving the debounce
acquisition into the dispatcher and guarding on an empty debounceOwner so it doesn't double up when it does come from a PendingDispatch.

I don't know if anyone else has tried this and confirmed it.

[faraweilyas]

@scabarcas17 yeah i confirmed it, it happens with queued Job listeners as well

[jackbayliss]

Bus::dispatch() is the raw path in my eyes, ie "push this job, no questions asked." the Bus methods dont respect this stuff, such as batch()

This also applies to other things like ShouldBeUnique etc.. so is defo intentional, I would suggest using Job::dispatch

[osteel]

Hmm I disagree. Debouncing is basically an attribute of the job, which should be honoured however the job is being dispatched. That should be true for all attributes IMO. Besides, people preferring dependency injection shouldn't be forced to use facades to get the expected behaviour (which is basically the case here).

I understand that a path allowing for pushing a job onto a queue while bypassing its attributes might be desirable, but it should be an explicit one IMO (e.g. Job::dispatchBypass(...), or something).

[osteel]

I keep getting bitten by this. I really think this is a problem.