Troubleshooting

If a bot does nothing, check these first: the bot and the strategy are both Active, the broker shows Connected, and the alert is written the way your checked examples were. The strategy's and the bot's Logs tabs then say what Nyria and the broker did with it.

Check these first

Most alerts that don't trade fail one of these:

• The bot is Active, not Paused
• The strategy is Active, not a draft
• The broker shows Connected on Integrations
• The alert is written the way the examples you checked were written
• The alert's ticker is one the bot trades
• The account has the buying power for the entry

Alert source issues

TradingView alerts not firing

Discord alerts not processing

Telegram alerts not processing

Strategy issues

Nyria couldn't read the alert

The strategy log row starts with ALERT FAILED: and gives the reason.

Fixes:

• Include the ticker, direction and action, spelled the way you checked them
• For options, write the strike and expiration the way your checked examples do
• Check it first in the alert tester, free and with no account
• Send the alert again

Ticker isn't in the strategy

The strategy log shows a Skipped row whose raw log line ends Rejected: instrument 'SPY' not in allowed list: [QQQ IWM], and the webhook answers 200 with the reason SPY isn't one of this strategy's tickers.

Fixes:

• Add the ticker to the strategy
• For crypto, name a pair the strategy selected. With only USDT pairs selected, BTCUSDC is refused as symbol BTCUSDC is not enabled for this strategy, while BTC and BTCUSD go through

Multiple entries disabled

The strategy log shows a Skipped row whose raw log line ends Rejected: a long SPY position is already open and Allow multiple entries is off.

Fixes:

• Wait for the current position to close
• Turn on Allow multiple entries on the strategy
• Check at the broker whether the position is open

No expiration matched the DTE range

When Nyria can name the nearest listed expiry, the strategy log row reads like No NVDA expiry within 1 to 3 trading days. The nearest is Fri, Oct 30 (4 trading days). Widen Days to expiration. Otherwise it contains no expirations found for SPY within 5-6 market days DTE, or with a minimum of 0 or 1, chain DTE 2 outside leg 1 range 0-1. The range counts trading days.

Fixes:

• Widen the DTE range so it includes a listed expiration. Many tickers list only weekly or monthly expirations
• Check the ticker has listed options
• Send the alert while the options market is open, when chain data is available

Strategy not active

The webhook answers 200 with a line such as Alert ignored: the strategy is a draft, and nothing trades.

Cause: the strategy is a draft, or needs its format checked again after a change to its alert types or option selection. A new strategy is a draft until its format is checked.

Fixes:

• On the strategy's Integration tab, enter an example alert for every enabled trade type
• Select Check format (Check and save in the TradingView wizard)

Bot issues

If a bot isn't trading, start with check these first.

Order rejected by broker

The bot log has the broker's reason. Nyria doesn't retry a rejected order, except one cash-account close, so a rejected exit leaves the position open until you close it.

Partial fill on spread

The filled legs are tracked, and the partial position stays open until the next exit alert closes them.

Fixes:

• Use market orders, which fill more often than limits
• On a limit spread, use a target that fills more readily: Ask for a debit spread, Bid for a credit spread
• Check which legs filled at your broker

Integration issues

Broker disconnected

The sign-in expired, the broker refused the credentials, or access was revoked or turned off at the broker. Bots on that integration place nothing until you reconnect, exits included.

1. On Integrations, select the broker.
2. Select Reconnect, then sign in at the broker again or enter a new API key.

An exit alert that arrives while it's disconnected is logged and notified but never sent. Positions stay open at your broker. See reconnect.

Sign-in to the broker fails

Allow pop-ups for the broker's site, then try again in a private window.

Position issues

No position found to exit

The strategy log shows a Skipped row whose raw log line ends Rejected: no open long SPY position to close.

Common reasons:

• An earlier exit already closed the position
• The entry alert never reached the strategy, or was rejected
• The exit names a different ticker than the entry

A bot log row whose raw line ends No position found is a different case: the strategy's position is open, but that bot holds none, for example because its entry never filled or was closed at the broker by hand.

Exit quantity exceeds position

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

The exit asked for more than the bot holds, usually because part of the position was closed outside Nyria.

Fixes:

• Compare the position size at your broker with the one on the bot
• If you closed part of it by hand, close the rest at your broker too

Spread exit with missing legs

The bot log shows Spread exit not sent: only some of its legs are open at your broker (missing: ...; open: ...). If none of the legs are open at the broker it reads Your broker shows no open position in any leg (...).

Some legs were already closed or never filled, so Nyria sends nothing and closes nothing. The log names the missing legs and the ones it found.

Fixes:

• Check the broker for legs closed by hand, and the entry's bot log for legs that never filled
• Close the remaining legs at your broker

Alert format check fails

Limit order with no price in the alert

The strategy log entry contains the SPY entry uses the Alert price, and the alert has no price. On an exit, the line says exit and ends Any open position is still open.

Fixes:

• Include a price in every alert
• Or change the limit target to Bid, Ask or Mid, or use market orders

Ambiguous crypto symbol

The strategy log entry contains ambiguous symbol BTC: this strategy trades more than one BTC pair (BTCUSDT, BTCUSDC), so send the exact pair in the alert.

Fixes:

• Name the exact pair in the alert: "BTCUSDT"
• Or select only one pairing on the strategy

Strike not listed in the option chain

The strategy log row reads like No SPY $781.5 call expiring Fri, Dec 18 is listed. The nearest are the $781 and $782 calls. Check the strike your alert names. When Nyria has no strike to name, it contains could not find option contract for strike 781.5 call expiring 2026-12-18; the strike may be invalid or not listed.

Fixes:

• Check the alert's strike against the chain at your broker. Strikes far from the money are often listed only at wider steps
• Check the expiration the alert names is a listed one

Getting help

Check logs first

1. Strategy logs: the strategy's Logs tab, for how each alert was read
2. Bot logs: the bot's Logs tab, for orders and broker responses
3. Details: open a row for the broker's exact response

Contact support

Include the strategy link, the bot's name, the time, the log row and your broker.

• Discord: join discord.gg/nyria, then open a ticket in #contact-us
• Email: contact@nyria.io

Next steps

• Free tools: build and check an alert message, or test one, before you send it
• Why is my bot not trading?: the six usual reasons a bot places no order
• Why was my exit skipped?: the five reasons an exit closes nothing
• What happens to an option that expires today?: the check before the close
• When an order fails: how to recover when a trade doesn't happen
• Known limitations
• Strategy logs: how each alert was read
• Bot management: pausing, editing and deleting bots
• Glossary