You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Deferred listeners: an oversized deferred entry or webhook payload is dropped, not delivered #4707
Left open as an author decision on the development → beta release #4580 (review thread #4580 (comment)), with a recommendation from #4669. Tracked here so it outlives the release PR.
The decision
An entry larger than the job argument budget (lib/Service/Deferral/ListenerDeferralService.php:375) is skipped with one error log line: the notification, webhook or projection it carried never runs and nothing retries it. #4669 left it open: an oversized deferred entry or webhook payload is still dropped and logged. The spec makes the drop the requirement ("SHALL be left out and logged").
Suggested direction
Degrade instead of drop: store the payload separately, re-enqueue a reduced entry, or run that one entry inline; update the spec scenario "One entry too large for any job" to match. Done when DeferredChunksFitTheJobLimitTest::testAnEntryTooLargeForAnyJobIsNamedAndTheRestGo asserts the large entry is still delivered in some form.
Activity
github-actions commentedon Oct 20, 2026
Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.
What happens next:
Triage labels:
triage:accept-feature— accepted as a new featuretriage:accept-bugfix— accepted as a bug fixtriage:needs-info— more information neededtriage:wontfix— will not be addressedtriage:duplicate— duplicate of another issue