The flush() method was ignoring the $force parameter and always flushing when jobs existed, violating the BatchHandlerInterface contract which states flushing "can be skipped if not" forced.

This caused inefficient batching behavior where flush(false) calls during worker idle periods would prematurely process partial batches instead of waiting for the batch size threshold to be reached.

What it does

Fixes BatchHandlerTrait::flush(bool $force) to respect the $force parameter:

• Before: flush(false) and flush(true) behaved identically - always flushed when jobs existed
• After: flush(false) only flushes when shouldFlush() returns true (batch size reached)

Example

$handler = new MyBatchHandler(); // batch size: 3

// Add 1 message (batch not full)
$handler->handle($message, $ack);

// Before fix: Would flush the 1 message
// After fix: Does not flush (waits for batch to fill)
$handler->flush(false);

// Always flushes (unchanged behavior)
$handler->flush(true);

Impact

This fixes the Worker's flush behavior during idle periods:

• Worker::run() calls flush(false) when no messages are handled
• Previously this would flush partial batches, defeating batching efficiency
• Now respects the intended batching behavior per the interface contract