> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/strategies/managing-strategies.md). # Managing strategies Every strategy can be paused, resumed, stopped, archived, deleted and cloned, and each has a linked strategy wallet. The details differ by type in ways that matter — especially which pauses survive a page reload or a different browser. ### Where to manage them * The **sidebar** lists every live strategy with a coloured status dot; click to open its detail page. * The **dashboard** table lists active strategies with pause/view buttons and drops stopped or completed ones. * The **list pages** (Trading → Cadence, DCA, Arbitrage) filter by status and search by name, asset or key. Grid and Rule-based have no list page; reach them from the sidebar or dashboard. * The **Archived** page shows terminal, read-only strategies. ### Statuses | Status | Meaning | | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | Running | Active. Each type also shows a finer reason when it is temporarily held (out of range, socket down, awaiting levels…) — see the strategy's page | | Paused | Held by you or by a condition; resumes automatically (conditions) or when you click Resume (your pause, circuit breakers) | | Stopped | Ended by you, or by an arbitrage risk stop. Not restarted automatically | | Completed | Set automatically only for Cadence, when every scheduled order is terminal | | Archived | Terminal and read-only; kept for records | ### Pause and resume | Strategy | Where the pause lives | Survives reload / another browser? | | ---------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | Cadence | Surge server | **Yes** | | Grid, Rule-based | Your browser (and the server pauses on its own when your tab disconnects) | No — a pause you set is local to this browser; the server still considers the strategy running and will resume trading in any other connected tab | | Arbitrage | Your browser (the server stops looking while no tab is connected) | No | | DCA | Your browser (the timer runs there); **Stop** is saved on the server | No (pause); yes (stop) | Circuit-breaker pauses on grid and rule-based are server-side and need an explicit **Resume**. **Pause All** in the header is a hold-to-confirm (1.6 s) kill switch that pauses every strategy at once, with the same per-type semantics as above. **Resume All** reverses it. ### Stop Stop ends trading. Open orders keep waiting for their fill or refund and are still shown; parked orders still need cancelling. Stopping does not move funds. A stopped strategy can be archived. For arbitrage, a strategy is also stopped automatically when it hits its daily loss limit or three consecutive losses. ### Archive Archiving is **permanent and read-only**: the strategy leaves the live lists and nothing about it can be changed. `[VERIFY: whether archiving also releases the strategy wallet link; deleting does.]` It stays visible under Archived with its history, and can be **cloned** to create a fresh copy. Rules: the strategy must not be running, and (for grid, rule-based, arbitrage and copy strategies) must have no order awaiting signature or open on chain. Cadence must be paused or completed. `[VERIFY: DCA can be stopped and archived from the Configuration tab.]` ### Delete Delete removes the strategy and its history (orders, cycles, schedule) from Surge and releases its wallet. It does not touch on-chain funds or open orders — cancel parked orders and empty the wallet first. Deleted strategies do not appear under Archived. ### Clone Grid, DCA, Arbitrage and Cadence strategies — live or archived — can be cloned into a pre-filled builder. Cloning is how you "edit" the settings that are immutable after creation (a grid's range, an arbitrage strategy's mode or wallets). `[VERIFY: rule-based plans have no clone option in the current build.]` ### Edit a running strategy | Strategy | Editable after creation | | ---------- | --------------------------------------------------------------------------------------------------- | | Grid | Name, description, boundary buffer | | Arbitrage | Name, description, profit/size/loss/reserve settings, allowed DEXes, status | | Rule-based | Name, description; levels (add/edit/delete/re-enable) | | DCA | Name, description, sizes and interval `[VERIFY: exact editable set]` | | Cadence | Name, description, volumes, duration, bounds, wallets — but the existing schedule is not re-planned | ### Linked wallets Each strategy's **Linked wallet** tab shows the strategy wallet, its balances and its orders. One wallet per strategy; Surge prunes links to strategies that no longer exist. A wallet whose key is not in this browser shows as *Not connected* and cannot sign — reconnect it from its key file. ### Drafts A builder keeps what you typed while you move around inside Surge (for example to generate a wallet) and clears it on a full page reload or after you deploy. ### Duplicate strategies A second live grid, arbitrage or cadence strategy with exactly the same wallet and settings as an existing one is refused. Archive the old one first, or change something. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.surgecardano.com/strategies/managing-strategies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.