Known Limitations
Important limitations to understand before using Nyria for automated trading.
Understanding these limitations is critical for successful automated trading. Failure to account for them can result in unexpected behavior and losses.
Platform Design Philosophy
Nyria is designed as a reliable, mid-frequency trade automation platform. We prioritize execution quality and stability over raw speed. This design philosophy means there are explicit limitations you should understand before automating.
Timing & Latency Limitations
Not Designed for High-Frequency Trading
Nyria is not intended for sub-second scalping or high-frequency trading strategies.
| Metric | Typical Range | Notes |
|---|---|---|
| Alert Processing | 100-500ms | Internal processing time |
| Total Latency | 200ms - 2s | Alert → Order at broker |
| TradingView Delays | 2-45+ seconds | TradingView considers 25-45s "normal" |
Not suitable for:
- Strategies requiring fills within milliseconds
- Sub-minute timeframe scalping
- High-frequency arbitrage
- Strategies sensitive to 1-2 second delays
Best suited for:
- 1-minute timeframes and above
- Swing trading strategies
- Options strategies (where seconds matter less)
- Position-based trading
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 |
| Telegram | Variable | API rate limits apply |
| TrendSpider | 1-5 seconds | Generally faster than TradingView |
| Custom API | Minimal | Depends on your implementation |
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 never 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
Why: Automatic retries can cause duplicate orders, position mismatches, and compounding errors. We believe manual review of failed orders is safer.
What to do:
- Monitor logs for failed orders
- Enable email notifications for trade failures
- Review and manually intervene when needed
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 email notifications for failures
- ✅ 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 all strikes may be available (liquidity dependent)
- Early assignment risk on short options
- Spread legs may fill at different times
- Options near expiration have heightened execution risk
- Index options (SPX, NDX) may have different trading hours
Cryptocurrency-Specific
- 24/7 markets = potential for overnight liquidation on leveraged positions
- Funding rates on perpetuals can erode positions
- Exchange-specific position and leverage limits
- Withdrawal limits may affect your ability to manage risk
Equities-Specific
- Pre-market and after-hours have limited liquidity
- Market orders become limit orders in extended hours (some brokers)
- Halts and circuit breakers can prevent execution
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 |
| 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/Telegram-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
Summary: Know Before You Automate
Before going live, honestly answer these questions:
- ✅ Can my strategy tolerate 30-60 second delays from signal to fill?
- ✅ Have I tested thoroughly with paper trading for at least 2 weeks?
- ✅ Do I understand that failed orders are NOT retried?
- ✅ Am I committed to checking my positions at least daily?
- ✅ Do I have a dedicated account (not mixed with manual trading)?
- ✅ If using TradingView, have I verified my strategy doesn't repaint?
- ✅ Do I have adequate capital for both entries AND exits?
- ✅ Do I understand the specific risks of my equity type (options, crypto, etc.)?
If you answered "No" to any question, stop and address it before going live.
Related Resources
- Risk Disclosure - Full trading risk documentation
- Troubleshooting - Common issues and solutions
- Alert Sources - Source-specific limitations
- Trading Behavior - Configuration options