Skip to content

Common Mistakes

This page addresses common misunderstandings and configuration mistakes when using Aurono.

Most issues are not errors.
They are expected outcomes of clearly defined rules.


Symptom:
“Nothing is happening.”

Explanation:
Aurono executes trades only when conditions are met at candle close.

If the market does not meet your configured conditions, Aurono does nothing.

This is normal behavior.


Confusing Intraperiod Movement With Signals

Section titled “Confusing Intraperiod Movement With Signals”

Symptom:
“The price touched my level, but Aurono didn’t act.”

Explanation:
Aurono ignores:

  • Intraperiod highs
  • Intraperiod lows
  • Temporary spikes or dips

Only the closed candle is evaluated.


Symptom:
“I set −4%, so why didn’t it buy at exactly that level?”

Explanation:
Percentages are evaluated relative to the previous candle close, not as fixed price targets.

Aurono does not track absolute price levels.


Symptom:
“The move was big enough, but nothing happened.”

Explanation:
All rules are evaluated on the selected timeframe.

A movement that appears large on a short timeframe may not qualify on a longer one.

Timeframe, percentages, and capital rules form one system.


Symptom:
“Sell trigger was met, but no sell occurred.”

Explanation:
Aurono will never sell below the strategy’s average cost base.

This safeguard applies to all strategies and cannot be disabled.


Symptom:
“Why did it only sell part of the position?”

Explanation:
Aurono sells according to the configured sell amount.

Partial sells are normal and expected.


Symptom:
“Why did it stop buying?”

Explanation:
Allocated capital defines a hard limit.

When fully used:

  • Buys stop automatically
  • No partial buys are placed

Aurono does not exceed this limit.


Symptom:
“Inconsistent behavior over time.”

Explanation:
Frequent parameter changes prevent a strategy from expressing its behavior.

Aurono executes rules consistently.
Constant reconfiguration interrupts that consistency.


Symptom:
Difficulty understanding results.

Explanation:
Multiple strategies increase complexity.

Start with:

  • One exchange
  • One asset
  • One strategy

Expand gradually once behavior is understood.


Symptom:
“Why doesn’t Aurono adapt?”

Explanation:
Aurono is execution-only.

It does not:

  • Optimize
  • Learn
  • Predict
  • Adjust strategies

All behavior comes from your configuration.


Aurono behaves predictably when understood correctly.

If something does not happen:

  • Conditions were not met
  • Safeguards prevented execution
  • Limits were reached

This is expected behavior.


Aurono is designed to enforce discipline, not activity.

Clear rules, applied consistently over time, are the foundation of its operation.