KITFORMA · EDITORIAL ANSWER
Why is a request-scoped bean unavailable inside a background task?
KitForma editorial guide. A background task can outlive the HTTP request supplying a scoped bean. A proxy neither preserves that completed request forever nor creates its context on an arbitrary worker.
Step-by-step answer
A background task can outlive the HTTP request supplying a scoped bean. A proxy neither preserves that completed request forever nor creates its context on an arbitrary worker.
Extract only immutable, authorized data the job needs during the request and pass it through a separate worker contract. Do not pass servlet requests, sessions or mutable security context into an unbounded job. Define retention and authorization checks for delayed work.
Test after the response completes and after the initiating account loses permission. Request scope is a lifecycle boundary, not durable asynchronous storage. Capturing the proxy in a lambda does not turn it into an independent snapshot.
Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This editorial answer was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.