Skip to documentation
Gimmer Desktop crypto automation
Download Latest release
Menu
Gimmer Documentation
Browse documentation

Operate

Keep every expected candle evaluation observable.

A running strategy must continue evaluating new closed candles whether it is in simulation or using real funds. Runtime activity, positions, orders, and health signals provide the evidence.

CurrentContinuous operation

Choose simulation first

Simulation uses current market data and the configured strategy without intentionally submitting real-money orders. Run it long enough to cross expected candle closes for every selected interval and market.

  1. Start the saved strategy in simulation. Confirm the mode shown in the strategy and bot status.
  2. Keep the runtime available. Prevent sleep or use a configured always-on host.
  3. Observe expected candle closes. A 4-hour strategy should evaluate each new 4-hour closed candle; a daily strategy only after the daily close used by its data source.
  4. Review positions and orders. Confirm the operation, amount, price, PnL, and final execution status.
  5. Investigate gaps. A missing expected evaluation needs attention even when no trade signal was expected.

Understand the live feed

Runtime activity is ordered newest first and loaded from persisted backend history as you scroll. The visible list is not the only copy of the data. Each event should preserve its closed-candle time so refreshed or paginated results remain correctly ordered.

Complete Gimmer live strategy view showing positions, operation types, schedule status, and AI Decision runtime activity
A healthy feed advances with the strategy interval even when the final action is hold.

Detect and recover a stalled strategy

SignalAction
Other strategies tick, one does notCompare that strategy's interval, selected markets, saved configuration, last candle, and runtime error.
All strategies stopCheck app process, sleep, network, exchange health, system clock, and always-on runtime.
Duplicate events or positionsDo not retry blindly. Preserve identifiers and timestamps so idempotency and reconciliation can be checked.
Activity advances but orders failOpen the execution detail and review balance, permission, minimum order, allowance, nonce, and venue status.
Feed looks oldCompare the displayed candle time with the configured interval and timezone before concluding it is stalled.

After a restart, Gimmer should reconcile the last processed candle and catch up missing closed candles without evaluating the same strategy/candle pair twice.

Start live execution

  1. Complete a representative backtest and a healthy simulation.
  2. Recheck connection permissions, free balances, markets, side, leverage, sizing, and risk controls.
  3. Read and accept the real-money trading terms presented by the app.
  4. Start with a small amount you can afford to lose.
  5. Monitor the first decision and every order attempt through a final state.

Live means external state changes

A network timeout does not prove that an order failed. Check the exchange or wallet state before retrying so a delayed confirmation does not create a duplicate position.

Stop safely

Stopping a bot does not necessarily close existing positions or cancel exchange orders. Review open positions, pending orders, and external account state. Decide explicitly whether to leave, reduce, or close exposure.