[13.x] [bug] Fix closure in chain not dispatched after batch completes

[JoshSalway]

Summary

Fixes a bug where a closure in Bus::chain is not dispatched when it follows a Bus::batch, throwing Call to undefined method Closure::getClosure().

Relates to laravel/serializable-closure#106

Root cause

The root cause is in serializable-closure's Native::__unserialize(). When deserializing a closure that captures an object with a SerializableClosure property, the objects restoration loop unconditionally calls getClosure() on all stored objects, including SerializableClosure instances that should be preserved as-is. This unwraps them to raw Closure objects, breaking any code that later calls getClosure() on the property.

PR laravel/serializable-closure#135 fixes this at the library level with an instanceof check before calling getClosure().

This PR (framework-level alternative)

If the serializable-closure fix is not accepted, this PR provides a framework-level workaround specific to ChainedBatch. It re-serializes $next to a string before capturing it in the finally closure, so the serializable-closure library never traverses into the CallQueuedClosure's properties:

$next = serialize($next);

$batch->finally(function (Batch $batch) use ($next) {
    if (! $batch->cancelled()) {
        Container::getInstance()->make(Dispatcher::class)->dispatch(unserialize($next));
    }
});

Reproduction

Bus::chain([
    new SomeJob,
    Bus::batch([new AnotherJob]),
    fn() => doSomething(), // This closure never runs
])->dispatch();
// Call to undefined method Closure::getClosure()

Test plan

• Integration test: testClosureAfterBatchInChainIsDispatched in JobChainingTest.php

[github-actions]

Thanks for submitting a PR!

Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.