Setting the file. One moment.
Subchapter 7.49
references/support-topics/post-response-work-waituntil.mdMarkdown1009 BView on GitHub
For stacks without Next.js after(), check whether non-critical work can run after the response instead of extending user-visible latency.
Inspect the listed route for analytics, logging, notifications, cache warming, metrics, or webhook side effects that happen after the response data is ready.
Do not move work that decides the response, must fail the request, changes visible state synchronously, or needs a durable retry guarantee.
Name the blocking side effect, the observed latency or upstream signal, and the exact line that can move behind waitUntil.