01

What you are doing

You are preventing new entries and allowing the runtime to handle any already-open strategy state according to the implemented stop 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/Stop disables new entries.
  2. 02A flat bot can become inactive after its runtime confirms no open strategy state.
  3. 03An open bot enters a draining/managed state until its defined safe completion condition is reached.
  4. 04After 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, DRAINING, PAUSED or STOPPED and continues reporting an open position until it is actually resolved.

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.