Troubleshooting

Why an alert did not trade, what a broker rejection error means, why a bot stays quiet, and how to reconnect a broker that disconnected.

Common issues and how to resolve them.

First, check the basics: Before troubleshooting, verify:

Bot is Active (not paused)
Strategy is Active (validated)
Integration is Connected (not reauth required)
Alert format matches what you validated

Alert Source Issues

TradingView Alerts Not Firing

Possible Causes:

Repainting strategy - Your strategy shows signals historically but doesn't fire them in real-time
Webhook delay - TradingView webhooks can be delayed 2-45+ seconds (they consider this normal)
Alert not triggered - Condition hasn't been met
Webhook URL incorrect - Typo or wrong URL

Solutions:

Verify your strategy doesn't repaint (learn more)
Wait up to 60 seconds for delayed webhooks
Check TradingView alert history to confirm it fired
Verify webhook URL matches exactly

Discord Alerts Not Processing

Possible Causes:

Bot not in channel - Nyria bot doesn't have access
Author filter mismatch - Alert sent by different user
Keyword filter mismatch - Alert doesn't contain required keyword
Message edited - Edited messages may not be re-processed

Solutions:

Verify Nyria bot is in the correct channel
Check author filter settings
Remove keyword filter to test
Send a new message (don't edit)

Strategy Issues

Alert could not be parsed

The strategy log shows an error entry that reads ALERT FAILED: AI parsing failed: <reason>.

Cause: Alert format doesn't match expected structure.

Solutions:

Ensure alert includes instrument, direction, and action
Check spelling of instrument names
For options, verify strike and expiration format
Review validated alert examples

Instrument not in the allowed list

The strategy log shows a warning entry ending Rejected: instrument 'SPY' not in allowed list: [QQQ IWM], and the webhook answers 200 with instrument not allowed: SPY.

Cause: Alert instrument not in strategy's allowed list.

Solutions:

Add instrument to strategy's allowed instruments
Check spelling matches exactly (SPY not Spy)
For crypto, ensure pairing matches (BTCUSDT not BTCUSD if only USDT selected)

Multiple entries disabled

The strategy log shows a warning entry ending Rejected: multiple entries disabled: open LONG position already exists for SPY.

Cause: Strategy doesn't allow multiple simultaneous positions.

Solutions:

Wait for current position to close
Enable "Allow Multiple Entries" in strategy settings
Check if position is actually open

No expiration matched the DTE range

The strategy log entry contains no expirations found within DTE range 0-1.

Cause: No listed expiration falls inside the strategy's DTE range.

Solutions:

Adjust DTE range to include available expirations
Check delta/price targets are reasonable
Verify instrument has options (not all stocks do)
Ensure market is open for option data

Strategy not active

The webhook answers 200 with Strategy is <status> - alerts are only processed for active strategies, and nothing trades.

Cause: the strategy is a draft, or it needs revalidating after a change to its alert types or option selection. A newly created strategy is always a draft until you validate it.

Solutions:

Go to the strategy's Integration tab
Fill in an example alert for every enabled trade type
Click Validate Alert Formats. TradingView strategies get a guided wizard instead
The status flips to Active once every example passes

Bot Issues

Bot not executing

Causes and Solutions:

Bot is paused:

Check bot status is Active
Click Start Bot if paused

Integration disconnected:

Check integration status
Reconnect if showing "Reauth Required"

Insufficient buying power:

Check broker account balance
Reduce position size
Close other positions to free capital

Instrument not selected:

Verify alert instrument is in bot's selected instruments
Add instrument to bot configuration

Strategy not active:

Check strategy status
Revalidate if required

Order rejected by broker

Common Causes:

Insufficient funds:

Check available buying power
Reduce position size
For spreads, ensure margin for max loss

Invalid option:

Strike not available
Expiration date passed
Contract doesn't exist

Account restrictions:

Pattern Day Trader limits
Options trading not enabled
Margin account required for shorts
Crypto not supported on account

Market hours:

Some order types restricted outside regular hours
Use limit orders for extended hours

Nyria does not retry a rejected order. If the rejection was on an exit, the position is still open; treat it as yours to close, by hand or with another exit alert. Only one narrow cash-account case is re-sent for you. See When an Order Fails.

Partial fill on spread

Cause: Some legs filled, others didn't.

What Happens:

Remaining legs tracked separately
Will exit on next exit signal
Partial position maintained

Solutions:

Use market orders for better fill rates
Widen limit prices for spreads
Trade more liquid options
Check broker logs for details

Integration Issues

Reauth required

Cause: OAuth token expired.

Solution:

Click the integration
Click Reconnect
Complete OAuth flow
Integration status updates

Bots on that integration stay paused until it reconnects, and nothing is retried once it does. See Reconnecting for the full flow and Notifications to be told the moment a connection goes stale.

Integration disconnected

Causes:

Token revoked at broker
Account closed
API access disabled

Solutions:

Check broker account status
Verify API permissions
Reconnect the integration
Contact broker support if needed

Disconnecting does not close open positions. Anything already open stays open at your broker until you close it. See When an Order Fails for the manual recovery path.

OAuth failed

The broker's sign-in window is where this breaks. Allow pop-ups for the broker's domain and try again in a private window.

Position Issues

No position found to exit

The strategy log shows a warning entry ending Rejected: no open positions found for SPY to close.

Cause: Exit alert but no open position exists.

What Happens:

Logged as WARNING (not error)
Any pending entry orders are cancelled
No trade executed

Common Reasons:

Position already closed
Entry never filled
Wrong instrument in exit alert
Position closed manually at broker

Exit quantity exceeds position

The bot log shows Exit quantity 3 exceeds position size 2.

Cause: Trying to close more than you have.

Solutions:

Check actual position size at broker
Verify position wasn't partially closed
Ensure bot position size matches reality

Spread exit with missing legs

The bot log shows spread exit aborted — partial position at broker (missing legs: ...). If none of the legs exist at the broker it reads spread exit aborted — none of the requested legs (...) exist as positions at the broker.

Cause: Some spread legs were already closed, or never filled.

What Happens: