Known limitations
What Nyria doesn't do, how fast it places orders, how late each alert source can run, and what to expect from retries, racing alerts and partial fills.
Timing
Built for 1-minute timeframes and slower
Sub-second, alert to order.
Fills depend on your broker and liquidity.
Alert source delays
TradingView can send an alert up to a minute late, and Discord, Telegram and TrendSpider add their own delivery time. Plan for 30–60 seconds. A Telegram alert that Nyria handles more than a minute after it was posted places no new entry. A close in it still runs.
Execution
No order retries
Nyria doesn't retry a failed or rejected order. The one exception is a close on a cash account that the broker rejected for a reason that clears by itself, such as unsettled funds or a broker outage: Nyria re-sends that close once, after re-checking the position at the broker. When an order fails covers recovery.
Alerts close together can race
Nyria doesn't guarantee the order of alerts sent close together. A sell alert sent right after a buy can arrive first, and two alerts that conflict can leave a position you didn't intend.
Leave at least 30–60 seconds between alerts, and don't build a strategy that sends conflicting ones. To flip a position, send one alert that reverses it rather than an exit followed by an entry. See flip between long and short.
Partial fills on spreads
Some legs of a multi-leg order can fill while others don't, which leaves the position unbalanced. Nyria tracks the legs that filled and exits them on the next exit alert.
Partial fills are most likely on thinly traded options with wide bid-ask spreads. Market orders fill more often, at the cost of more slippage. If you suspect a partial fill, check the position at your broker.
Position tracking
Nyria tracks the orders it placed
Nyria tracks the orders it placed, not everything in the account. Its record drifts from your broker when:
- You trade the same account by hand
- Another system trades the same tickers
- An order recorded as failed did execute, which is rare
- The broker changes the position itself, as in a split or other corporate action
Give Nyria an account of its own, with no manual trades in it.
Exit alerts need an open position
When an exit alert arrives and Nyria tracks no open position, it sends nothing to the broker and logs the alert as Skipped, not Failed. If you expected a position, Nyria's record may have drifted from your broker's.
What can go wrong
| Issue | Effect | Where you see it |
|---|---|---|
| Broker disconnected | No orders, exits included, until you reconnect | Integrations shows Disconnected |
| Alert source outage | Alerts never reach Nyria | No entry for them on the strategy's Logs tab |
| Order rejected | The trade doesn't happen | The bot's Logs tab, with the broker's reason |
| Partial fill | The spread is unbalanced | Your broker's positions page |
| Market gap | A worse fill than the alert price | The fill price on the bot's log |
| Repainting strategy | Live trades differ from the backtest | Repainting |
Run the daily check to catch these.
Broker-specific limitations
All brokers
Order types and extended-hours rules differ by broker and asset type. Each broker's page under integrations lists what it takes.
Options-specific
- Nyria trades only strikes listed in the option chain
- Your broker can assign a short option early, and Nyria doesn't see the assignment
- Index options (SPX, NDX) have different trading hours from the ETFs that track them
What Nyria doesn't do
Nyria doesn't give investment advice or trade recommendations, guarantee fills or profit, or detect repainting. It doesn't place bracket, OCO, OTO, trailing-stop or attached take-profit orders: exits come from exit alerts.
Alert sources
TradingView-specific
- Options strategies always use From my rules
- TradingView can send an alert up to a minute late
- Repainting strategies fail: see TradingView repainting
- TradingView doesn't guarantee webhook delivery
Discord-specific
- Every alert needs a ticker, a direction and an action
- A caller who changes their display name stops matching the author filter. To move to a new channel, pick it on the strategy
- Discord's rate limits can delay when Nyria reads a message
- Edited messages are not read again
Telegram-specific
- An alert that Nyria handles more than a minute after it was posted, or after a newer message for the same strategy, places no new entry. A close in it still runs
- Messages that other bots post in a group aren't read
- Edited messages are not traded
- Messages posted before Nyria joined the chat can't be read
- If Nyria is removed from the chat, or you stop being one of its admins, the strategy stops reading it
Custom webhook
- Past 10 alerts at once, then 1 a second, the webhook answers
429. See the webhook reference
Related
- Risk disclosure: every trading risk
- When an order fails: how to recover when a trade doesn't happen
- Paper trading: what a simulated fill does not test
- Troubleshooting: common problems and fixes
- Alert sources: limits of each source
- Trading behavior: strategy settings
Security and your money
What a broker connection lets Nyria do, why it can't withdraw your money, how to revoke access, and how tokens and API keys are encrypted at rest.
Risk disclosure
The risks of automating trades with Nyria, including order failures, market gaps, connectivity loss and the potential total loss of capital.