> For the complete documentation index, see [llms.txt](https://nfa.gitbook.io/nfa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nfa.gitbook.io/nfa-docs/platform-and-reliability.md). # Platform and reliability ## Platform and reliability NFA runs long, expensive, stateful forecasts, so the platform is built to keep them alive and to fail safe. ### The main ideas * **Backpressure.** A run gate caps concurrent and in-flight runs; past the ceiling, new requests are queued or rejected cleanly rather than overwhelming the engine. * **A durable queue.** Runs past a user's concurrency cap are persisted and dispatched by a single-holder scheduler, so a restart never loses queued work. * **Self-healing.** Advisory-locked sweepers recover orphaned and stuck runs and requeue stranded jobs. * **Safe streaming.** Live runs stream over server-sent events with heartbeats, consumed by a fetch-based reader so the client can authenticate. * **Guarded edges.** Rate limiting, CORS ordering, and security headers are arranged so that failures surface as clean errors rather than opaque ones. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://nfa.gitbook.io/nfa-docs/platform-and-reliability.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.