# Emergency Operations and Recovery

**`emergency_pause(...)`**, **`resume_after_emergency(...)`**, **`emergency_withdraw(...)`**\
**Purpose**: Protect liquidity and user funds in case of bugs, exploits, or other unforeseen issues.\
**Process**:

* Temporarily deactivate trading or liquidity changes.
* Allow the pool owner to remove NFTs and tokens if necessary to prevent losses.
* Ensure these operations are restricted to authorized addresses and subject to cooldowns.

**Use Cases**:

* Responding to a smart contract vulnerability or market anomaly.
* Providing user confidence in the event of unexpected problems.

**Best Practices**:

* Use emergency features sparingly and transparently.
* Communicate with users when pausing and resuming pool activities.


---

# 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.artinals.com/artinals-protocol/trade-module/functions-and-entry-points/emergency-operations-and-recovery.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.