Skip to main content
Owly submits strategy actions to Hyperliquid and refreshes account state as execution results become available. Copying, exchange acceptance, fills, and portfolio updates are separate stages.

​
What affects execution

A submitted order may remain open, fill partially, or be rejected. A successful start request means the strategy request was accepted, not that all source positions have already been copied.

​
Copying and synchronization

Copy settings include periodic position, spot, leverage, and optional pending-order synchronization. Each has its own enabled state and interval. A synchronization interval is not an end-to-end execution guarantee. LeverAcc does not support copying pending orders. Grid Bot reconciles its configured grid on its own interval. Its behavior and account requirements are described in Grid Bot.

​
Check results

  1. Check the bot’s current state and any reported error.
  2. Inspect actual orders and fills, including partial or rejected orders.
  3. Compare the same market and account scope before judging a difference from the source.
  4. After stopping or closing, inspect remaining orders, positions, and cleanup status.
Owly’s source implementation does not establish a fixed latency or slippage guarantee. Market conditions and upstream availability affect the outcome. See Troubleshooting when execution differs from expectations. For the team’s asynchronous Hyperliquid SDK, see async-hyperliquid. SDK benchmarks describe their own test conditions and should not be treated as a guaranteed user trade latency.