# Manage a deployment > Pause, resume or stop one strategy, change its limits without stopping it, read the running-version notice, and use the account menu to pause, cancel or close everything on an account. Source: https://orbitalaip.com/docs/trade/manage-a-deployment > [!IMPORTANT] Disclaimer > Backtest results are hypothetical and do not predict future performance. Nothing here is investment advice: Orbital computes the rules you supplied and recommends nothing. Orbital is not a registered investment adviser or broker-dealer. Costs are as modelled by the chosen cost profile and may differ from live trading. ## Open the deployment page Every running [deployment](https://orbitalaip.com/docs/glossary#deployment) has a page, headed with the strategy's name and **Change its limits and what it may do on its own.** Only workspace owners and admins can use it. 1. **Open Deployments** In Trade, click **Deployments** in the header. A **Running** row carries **Pause** and **Stop**, a **Paused** one **Resume** and **Stop**, and a **Stopping** one neither. 2. **Open the page** Click the chevron at the end of the row. A strategy's own page under **Strategies** opens the same panel from **Manage**. The page has **Version**, **Limits** and **Trading permission** sections, and a **Now** panel with the row's buttons and **Save limits**. Each act is recorded in [Activity](https://orbitalaip.com/docs/trade/pnl-orders-and-activity#activity), with who or what made it. ## The running-version notice **Version** reads **Runs v1**, adding **main is v3** once [main](https://orbitalaip.com/docs/glossary#main) moves on; to run another version, stop this one and deploy that. See [Editing a strategy after it is deployed](https://orbitalaip.com/docs/trade/deploy-a-strategy#editing-a-strategy-after-it-is-deployed). ## Pause and resume To pause a running deployment: 1. **Click Pause** A confirmation opens under the row, or under **Save limits** on the deployment's page. It reads **New trades stop. Exits keep working.** and **It stays paused until it is resumed.** 2. **Click Pause strategy** **Cancel** backs out. Orbital can pause a deployment itself, for example when it reaches its **Daily loss pause** or when what it was deployed with no longer holds. The row then reads **New trades paused** followed by the reason, and the person who deployed it gets a notification. To resume a paused deployment: 1. **Click Resume** The confirmation reads **New trades start again at its next decision, within its limits.** It says why it was paused, and for a cause Orbital keeps checking it adds **If that still holds, it is paused again.** 2. **Click Resume strategy** **Keep it paused** backs out. ## Stop 1. **Click Stop** The confirmation reads **Stopping is final: it never trades again, and it cannot be resumed.** Nothing is sold: what it holds is left to its own exits. To close a position now, close it from **Positions**. 2. **Click Stop strategy** **Keep it** backs out. A deployment that still holds something reads **Stopping** until its own exits have closed what it holds; one already flat stops at once. Once stopped, it leaves the **Running** list, and the strategy can be deployed again. Its limits can no longer be changed. ## Change the limits The four limits and the trading permission can change while the deployment runs. [The four limits](https://orbitalaip.com/docs/trade/capital-sleeves#the-four-limits) explains each one. 1. **Edit the limits** **Budget**, **Max per trade** and **Daily loss pause** take a percentage or dollars, switched with the **%** and **$** buttons. **Open positions** and **Daily loss pause** may stay empty for no limit. 2. **Pick a trading permission** A Rules or Program strategy stays on **Always-approve**, and an Agent strategy cannot take a mode wider than its agent's own permission. See [The trading permission](https://orbitalaip.com/docs/trade/approvals-and-permissions#the-trading-permission) and [The agent's own permissions](https://orbitalaip.com/docs/trade/approvals-and-permissions#the-agents-own-permissions). 3. **Click Save limits** Lowering a limit opens a confirmation that reads **This lowers what it may do.** Raising one reads **This lets it take on more. Check each change before it applies.** and lists each change, old to new. A larger limit, a limit removed, a looser permission, or a limit moved between dollars and a percentage counts as a raise. 4. **Click Save limits again** **Back** returns to the form. The answer reads **Saved. Every new trade is checked against these limits.** The new limits apply from the strategy's next trade, including entries already waiting to be sent. ## The account menu The **⋯** button at the right of the header opens the account menu, headed with the account's name. Every row acts on that account only, in every project that trades it. - **Pause all strategies**: **New trades stop. Exits keep working.** - **Cancel all open orders**: **Includes exits, so positions lose their stops.** - **Close all positions**: **Sells everything, and buys back anything short, at market.** - **Stop everything…**: **All three, in a safe order. Other accounts keep running.** 1. **Pick a row** A confirmation repeats the row's line. **Stop everything…** opens its own dialog instead. 2. **Confirm** The button names the act, for example **Cancel all orders** or **Close 7 positions**. **Keep them** or **Cancel** backs out. **Close all positions** also pauses each strategy that held one of those positions, with the reason **one of its positions was closed by hand**. No order is shown as canceled, and no position as closed, until Alpaca confirms it. There is no resume-all. After a pause, resume each strategy from its own row. ### Stop everything **Stop everything…** opens a dialog listing its three steps, each waiting for the one before it. It names this project's strategies, but pauses every strategy on the account, in every project. 1. **Check the scope** The note reads **Only this account.** and names any other connected account, which keeps running. 2. **Click Stop everything** When the market is closed, it asks **The market is closed. How should the positions be closed?** **Queue for the open** sends market orders that fill when the next session opens. **Limit orders now** sends limit orders at the last price, working in extended hours. Then click **Stop everything** again. 3. **Follow the progress** Each step shows a mark and its count. The last reads **Closed 7 positions** only once Alpaca confirms every fill. 4. **Close the panel when you like** It keeps going, **Activity** records every step, and the menu's **Stop everything…** row reopens the panel. Until it finishes, new orders, cancels, closes and deploys on the account are refused. If it could not finish, the title reads **Could not stop everything on** the account, and it says what to check. > [!WARNING] > **Stop everything…** closes every position on the account, including positions placed by hand. A plain **Stop** on one strategy sells nothing; use it when that strategy's own exits should close what it holds.