Setting the file. One moment.
Subchapter 7.32
references/support-topics/fluid-compute-caveats.mdMarkdown1 KBView on GitHub
Fluid compute is a project-level lever. Use it when the setting is off and metrics show cold-start or warm-instance reuse pressure. Fluid can handle multiple invocations in one function instance; avoid per-request state in module scope.
Check project facts, startTypeSplit, cold-vs-warm latency, and routes carrying the cold-start share. When enabling Fluid, audit module-state hazards Fluid surfaces (not creates): module-scoped mutable state, lazy singletons holding per-user data, globals keyed on per-request inputs.
Do not recommend enabling fluid compute when project facts say it is already on. Do not frame as a file-level code fix.
State project setting, cold-start rate or fallback slow-route signal, affected route concentration. If enabling, call out module-state audit as follow-up.