# Handling Staleness and Plane Failure

If a plane stops reporting or becomes stale:

* Its value is excluded from NAV.
* Its strategies are frozen until updates resume.
* The vault operates normally using available zkSync liquidity.
* Withdrawals remain functional via local reserves and queued unwinds.

In this scenario, the system remains solvent and predictable.


---

# Agent Instructions: 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:

```
GET https://multistake-1.gitbook.io/multistake-docs/documentation/oracle-architecture/validation-pipeline/handling-staleness-and-plane-failure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.