Skip to content

Troubleshooting

This page lists common issues and situations that can occur during Aurono setup and strategy execution.

Most issues are not errors, but expected outcomes of configuration, safeguards, or external constraints.

Work through this page step by step before assuming something is broken.


Possible causes:

  • Aurono is not powered on
  • Device has not finished booting
  • Network connection is unavailable
  • You are not on the same local network

What to check:

  • Wait at least 2 minutes after powering on
  • Verify the Ethernet cable is connected
  • Ensure your browser device is on the same network
  • Try refreshing the page or another browser

The Device Was Reachable Before, But Not Anymore

Section titled “The Device Was Reachable Before, But Not Anymore”

Possible causes:

  • IP address changed
  • Network was changed
  • Device lost power

What to check:

  • Power connection
  • Network cables and connections
  • Router or network changes

Aurono does not expose itself externally.


Possible causes:

  • Incorrect API key or secret
  • API permissions are insufficient
  • API key was revoked or expired

What to check:

  • API key and secret were copied correctly
  • Required permissions are enabled
  • Withdrawal permissions are disabled
  • API key still exists on the exchange

Re-enter credentials if in doubt.


Possible causes:

  • Incorrect ECDSA key formatting
  • Wrong portfolio selected
  • Key Name and Private Key swapped

What to check:

  • The Key Name field contains the CDP key name (starts with organizations/...)
  • The PEM key field contains the private key (starts with -----BEGIN EC PRIVATE KEY-----)
  • ECDSA is selected when generating the key on Coinbase
  • Primary (Standard) portfolio is used

Exchange Is Connected, But No Balances Are Shown

Section titled “Exchange Is Connected, But No Balances Are Shown”

Possible causes:

  • Balance permissions are missing
  • Asset is held in a different portfolio or wallet
  • Exchange API is temporarily unavailable

What to check:

  • API permissions
  • Correct exchange selected
  • Exchange status page

This is the most common situation.

Possible reasons:

  • Buy or sell conditions were not met
  • Candle has not closed yet
  • Timeframe is long
  • Allocated capital is fully used
  • Strategy is in shadow mode (no real orders are placed)

What to check:

  • Check the Activity feed — every evaluation is logged with the reason
  • Timeframe and trigger thresholds
  • Available allocated capital
  • Whether the system is in shadow or live mode (Settings)

Inactivity is normal.


Price Reached My Level, But No Trade Occurred

Section titled “Price Reached My Level, But No Trade Occurred”

Explanation: Aurono evaluates only closed candles.

Intraperiod highs and lows are ignored.

What to check:

  • Did the candle close beyond the trigger?
  • Is the timeframe correct?

Possible causes:

  • Allocated capital fully used
  • Buy amount exceeds remaining allocation
  • Order size below exchange minimum
  • Strategy disabled at evaluation time

Aurono does not place partial or adjusted orders.


Sell Trigger Was Met, But No Sell Occurred

Section titled “Sell Trigger Was Met, But No Sell Occurred”

Possible causes:

  • Sell price was below average cost base
  • Insufficient asset balance
  • Order size below exchange minimum

Aurono will never sell below average cost base.


Most common cause:

  • Allocated capital is fully used

Aurono will not:

  • Borrow
  • Reduce order size
  • Exceed limits

This is expected behavior.

Explanation:

  • Sell amount limits how much is sold per trade
  • Partial sells are normal
  • Remaining assets continue to be tracked

Explanation: Allocated capital is a limit, not a guarantee of usage.

Aurono deploys capital only when conditions are met.


Explanation: Aurono waits for:

  • Candle close
  • All conditions to be satisfied

It does not react intraperiod.


Possible causes:

  • Long timeframe
  • Conservative triggers
  • Market conditions

This is not an error.


Aurono Did Nothing During a Crash or Spike

Section titled “Aurono Did Nothing During a Crash or Spike”

Explanation:

  • Intraperiod movement is ignored
  • Only closed candles matter
  • Safeguards may block execution

This is expected behavior.


Possible causes:

  • Strategy disabled
  • Exchange connection lost
  • Credentials revoked

What to check:

  • Strategy status
  • Exchange connection test
  • Settings page

Strategy Was Running But Stopped Evaluating

Section titled “Strategy Was Running But Stopped Evaluating”

Possible causes:

  • Strategy was paused or archived
  • System was switched back to shadow mode
  • Exchange credentials were revoked or expired

What to check:

  • Strategy status on the Strategies page (Running / On hold / Archived)
  • System mode in Settings (shadow / live)
  • Exchange connection test in Settings

Consider further action if:

  • Dashboard does not load after power and network checks
  • Exchange connection consistently fails
  • Errors are shown in the dashboard
  • Configuration is correct but behavior is inconsistent over time

Otherwise, the system is likely behaving as designed.


Aurono is deterministic.

If something does not happen:

  • Conditions were not met
  • Limits were reached
  • Safeguards applied

This is expected behavior, not a malfunction.


If issues persist:

  • Review the Strategy Builder section
  • Double-check configuration
  • Simplify setup (one strategy, one asset)
  • Contact support with:
    • Exchange
    • Strategy settings
    • Observed behavior