Known Limitations
What Nyria will not do for you: almost no order retries, no guaranteed fills, no repaint detection, plus the measured latency and alert delays to plan around.
Understanding these limitations is critical for successful automated trading. Failure to account for them can result in unexpected behavior and losses.
Timing & Latency Limitations
Not designed for high-frequency trading
Nyria is not built for sub-second scalping. Anything on a 1-minute timeframe or slower is what it is for.
| Metric | Measured | Notes |
|---|---|---|
| Parse to order | median 0.63s, p90 1.33s | Across 15,001 production orders. From the parsed alert landing to the order being written |
| Fill after the order | Not measured here | Broker and liquidity dependent |
| TradingView delays | 2-45+ seconds | Before Nyria sees anything. TradingView considers 25-45s "normal" |
Alert Source Delays Are Outside Our Control
Third-party alert sources may experience delays that Nyria cannot predict or compensate for:
| Source | Typical Delay | Notes |
|---|---|---|
| TradingView | 2-45+ seconds | Platform considers 25-45s delays "normal" |
| Discord | Variable | Depends on message queue |
| Custom webhook | Minimal | Depends on your implementation |
| TrendSpider | Variable | Depends on TrendSpider's own alert engine |
(Telegram is coming soon and not yet included here.)
Nyria cannot control or compensate for third-party alert delays. Your strategy should be designed to accommodate potential delays of 30-60 seconds from your alert source.
Execution Limitations
No Order Retry Logic
Failed or rejected orders are not automatically retried.
- If a broker API call fails, the order is logged as failed
- If a broker rejects an order, no automatic retry occurs
- Network timeouts result in order failure, not retry
- No entry is ever re-sent
Why: Automatic retries can cause duplicate orders, position mismatches, and compounding errors. We believe manual review of failed orders is safer.
The one exception re-sends a close, once, on a cash account whose exit was rejected for unsettled funds, after checking the position still exists at the broker. When an Order Fails sets out every condition.
What to do:
- Monitor bot logs for failed orders. The log is the complete record
- Enable email notifications for trade failures. See Notifications
- Review and manually intervene when needed
Notifications catch failures the bot flags at the moment it places the order. A rejection the broker reports late is written to the bot log without raising a notification or an email, so an empty inbox is not proof that nothing failed. When an Order Fails covers the whole picture.
Race Conditions Can Occur
If you send multiple signals in rapid succession:
- Order of execution is not guaranteed
- A sell signal sent 100ms after a buy may arrive first
- Conflicting signals can cause unexpected position states
Best Practices:
- Leave at least 30-60 seconds between signals
- Design strategies that don't send conflicting signals
- If flipping positions, use a single signal (not exit + entry)
Partial Fills on Spreads
For multi-leg option orders:
- Some legs may fill while others don't
- Nyria tracks partial positions and will exit remaining legs on next exit signal
- You may temporarily have unbalanced positions
What to do:
- Check broker account if you suspect partial fills
- Use market orders for better fill rates (more slippage)
- Trade liquid options with tighter bid-ask spreads
Position Tracking Limitations
Nyria Tracks Based on Successful Executions
Our position tracking assumes:
- All successful orders are accurately reflected in your broker account
- No manual trades occur in the same account
- No other systems are trading the same instruments
Position Mismatch Risks:
- Manual trades at your broker can desync tracking
- Failed orders that actually executed (rare but possible)
- Broker-side adjustments (corporate actions, etc.)
Best Practice: Use a dedicated account for Nyria automation. Don't mix manual trading with automated trading in the same account.
Exit Signals Require Open Positions
If you send an exit signal but Nyria doesn't track an open position:
- The signal is logged as a WARNING (not error)
- No order is sent to broker
- This could indicate a tracking mismatch
Not "Set and Forget"
Automated trading requires active monitoring. This is not a passive income system. Things can and will go wrong.
What Can Go Wrong
| Issue | Frequency | Impact |
|---|---|---|
| Broker disconnection | Occasional | Trades stop until reconnected |
| Alert source outage | Rare | Missed signals |
| Order rejection | Common | Trade not executed |
| Partial fills | Occasional | Unbalanced positions |
| Market gaps | Common | Worse fills than expected |
| Strategy repainting | User error | Completely different live vs backtest results |
Minimum Monitoring Requirements
You must commit to:
- ✅ Checking positions daily (minimum)
- ✅ Reviewing logs after significant market events
- ✅ Watching for reauthorization notifications
- ✅ Monitoring notifications for failures, in-app and by email
- ✅ Periodically verifying Nyria positions match broker positions
Broker-Specific Limitations
All Brokers
- Order types supported vary by broker and instrument
- Extended hours trading rules vary by broker
- Margin requirements are enforced by broker, not Nyria
- Pattern Day Trader (PDT) rules apply to accounts under $25k
Options-Specific
- Not every strike is listed. Nyria cannot buy one that has never traded
- Short options can be assigned early, by the broker, without Nyria seeing it
- Spread legs can fill at different times, leaving the position unbalanced
- Index options (SPX, NDX) keep different hours from the ETFs that track them
What Nyria Does NOT Do
To set clear expectations, here's what Nyria explicitly does not provide:
| What We Don't Do | Why |
|---|---|
| Investment advice | We're a technology platform, not advisors |
| Trading recommendations | You decide what to trade |
| Guarantee order execution | Broker and market conditions control fills |
| Guarantee profitability | Markets are unpredictable |
| Retry failed orders | Too risky for automation. One narrow exception re-sends a cash-account close |
| Manage your broker account | That's your responsibility |
| Verify alert source quality | You must test your own strategies |
| Detect repainting strategies | Requires manual verification |
| Monitor positions 24/7 for you | You must actively monitor |
Strategy/Alert Source Limitations
TradingView-Specific
- Must use Internal Selection for options (TradingView has no option data)
- Alerts can be delayed 25-45+ seconds
- Repainting strategies will fail - see TradingView Repainting
- Webhook delivery is not guaranteed
Discord-Specific
- Message parsing relies on consistent format
- Author changes or channel changes break the connection
- Rate limits may delay message retrieval
- Edited messages may not be re-processed
Custom API-Specific
- Rate limiting applies
- Authentication via webhook URL token
- No acknowledgment beyond HTTP response
Related Resources
- Risk Disclosure - Full trading risk documentation
- When an Order Fails - The recovery path when a trade does not happen
- Paper Trading - What a simulated fill does not test
- Troubleshooting - Common issues and solutions
- Alert Sources - Source-specific limitations
- Trading Behavior - Configuration options
Security & Your Money
Whether Nyria can move your money, what a broker connection actually lets it do, how to revoke it in one click, and what is encrypted and what is not.
Risk Disclosure
The risks of automating trades with Nyria, including order failures, market gaps, connectivity loss and the potential total loss of capital.