# Position Rollovers

<figure><img src="/files/PWzxerylrY3Pbvttkgpq" alt=""><figcaption></figcaption></figure>

Position Rollovers allow operators to maintain operational continuity without triggering bounded liquidation. They provide a controlled method to refinance temporary deficits by using unused credit lines or re-allocating backing assets — which can improve the Health Factor (HF), maintaining the stability of delegated YODL.

### Mechanism &#x20;

#### Deficit Detection

The HF is viewable on the operator dashboard, and as it approaches 1.0, it indicates a potential deficit based on mark-to-market asset values and applied haircuts. The operator may elect to perform a rollover before liquidation triggers.

#### Credit Re-allocation

The operator rolls over exposure from one [Orchestrator](/technical-components/smart-contracts.md#orchestrator-per-execution-vault-per-operator) (per-vault) to another (e.g., WETH → USDT) by activating their unused credit capacity (unutilized balances) of the other asset. Rollovers can also be performed within the same asset across Orchestrators for repayments.

#### Market Execution

The rollover transaction is executed atomically through the Orchestrator using whitelisted AMMs. The Operator incurs standard slippage and taker fees.

#### Accounting Update

Managing exposure via rollovers may improve HF.

#### Repayment Obligation

All rollover-borrowed credit must be repaid before the epoch ends; otherwise, it is treated as outstanding exposure requiring restoration through delegated $YODL being slashed under the protocol’s restoration process, which also impacts operator reputation.


---

# 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://docs.yodl.fi/capital-access-and-protection/risk-mitigation/position-rollovers.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.