Market movement
A strategy can follow its rules and still lose when price behavior differs from its assumptions. Repetition does not make a weak rule profitable.
Stryx Learn / risk
Crypto trading bot risks and failure modes
Automation can repeat configured actions, but it also combines market exposure with software, data, wallet and venue dependencies. The applicable risks depend on the selected workflow; not every service uses every dependency listed here.
Market and leverage risk
Leverage and liquidation
Leveraged positions can amplify losses and approach liquidation quickly. An automation runtime may not reduce exposure before venue thresholds are reached.
Execution and liquidity failures
Slippage, spread and thin books
The executable price can differ from a trigger or quote. Wider spreads and low depth can worsen fills as order size increases.
Partial fills
An order may fill only partly, leaving unexpected exposure or an incomplete hedge that the next strategy cycle does not anticipate.
Rejected or delayed orders
Venue rules, balance changes, rate limits, invalid parameters or connectivity can reject or delay an instruction while markets continue moving.
Venue, API and stale-state risk
Unavailable venue or API
A service may be unable to read state or submit actions during venue maintenance, API failure, rate limiting or network interruption.
Stale prices
A delayed feed can make a rule evaluate old information. A displayed price or runtime state should not be treated as proof of current venue state.
Restart and recovery uncertainty
After a process or connection restarts, local intent can differ from live orders and positions. Reconcile current venue state before resuming where the service provides that control.
Wallet, key and configuration risk
Delegated-key exposure
Where a workflow uses an executor or delegated signer, compromise or unintended authority can produce actions within the available scope. Protect devices, sessions and credentials.
Configuration mistakes
Wrong size, direction, market, distance, threshold or mode can execute consistently while remaining inconsistent with the user’s intent.
Funding mismatch
Insufficient collateral, gas or executor-wallet balance can block expected actions. Excess funding can increase the amount exposed to operational error.
Other dependencies where relevant
Some workflows can depend on smart contracts, bridges, oracles or blockchain networks; others interact directly with a venue API and do not use all of those components. Confirm the actual path for the selected service before assigning a risk to it.
Monitoring and manual intervention
Watch reality, not only intent
Compare reported runtime state with venue orders, positions, wallet balances and errors. Investigate stale timestamps or unexpected exposure.
Know when to stop
Intervene when execution errors repeat, liquidity deteriorates, permissions change, data is stale, venue access fails or the strategy’s assumptions no longer hold.