# Handling Asynchronous Execution

External execution environments operate independently of zkSync’s timing and settlement cadence. As a result, rebalancing must account for:

* Variable execution latency and confirmation delays.
* Cross-domain asset transfer and messaging latency.
* Heterogeneous block production and settlement characteristics.
* Environment-specific failure and recovery modes.
* Partial-return and intermediate settlement states.

To preserve accounting correctness under these conditions, the zkSync vault maintains explicit *pending rebalance* states that track:

* Capital expected to return from in-flight unwinds.
* Capital reserved for pending allocations.
* Strategy deltas awaiting validation and reconciliation.
* Discounted or provisional values for incomplete execution cycles.

This state tracking ensures that `totalAssets()` and NAV remain conservative, deterministic, and correct at all times, even while cross-environment execution is in progress or partially complete.


---

# 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/rebalancing-and-routing/handling-asynchronous-execution.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.