01

What you are doing

Pause, Resume and Stop are separate confirmed controls. Pause blocks new cycles without ending the deployment. Resume allows new cycles again. Stop begins the safe shutdown policy.

02

Why it matters

Immediate abandonment of an open leveraged position can be unsafe. HEDGERON separates stopping new entries from completing or safely handling an existing cycle.

03

Before you start

Read current position, orders, Shield state and bot status. Do not assume Stop means instant market closure.

04

Step by step

  1. 01Pause blocks new cycles while the deployment remains active and existing positions and Shield protection remain managed.
  2. 02Resume re-enables new cycles only after the server confirms the transition.
  3. 03Stop blocks new entries immediately. A flat bot becomes STOPPED; a bot with an open position becomes DRAINING until the managed cycle reaches its safe completion condition.
  4. 04While a bot is DRAINING, Start new cycles cancels the pending stop and returns the bot to ACTIVE without interrupting the managed position.
  5. 05After membership expiry, no new entries are created; an already-open cycle continues to the implemented safe completion state.
05

What you should see

Dashboard identifies ACTIVE, PAUSED_NEW_ENTRIES, DRAINING or STOPPED and continues reporting an open position until it is actually resolved. DRAINING shows Start new cycles so the pending stop can be cancelled.

06

Security check

Do not revoke API access while a managed position remains open unless an incident procedure requires immediate revocation.

07

Common problems

Stop did not close immediately

That is expected when a cycle is being drained rather than abandoned.

Membership expired with an open cycle

New entries stop; monitor the existing cycle until the defined completion state.

08

Next step

Review the full HEDGERON security model.