Guide
Why is my trading bot not placing orders?
Open the bot's Logs tab: the newest rows say which state it is in. The usual causes are a paused bot, an expired broker connection, a budget per entry below one unit, a ticker filter, an account the strategy doesn't allow, the strategy's own rules, or an alert that never arrived. Each has one fix, and Nyria doesn't retry a refused order.
Official documentation
Find why a bot placed nothing
- 1
Read the bot's Logs tab
Open the bot from My bots. The newest rows show each alert and what became of it, with a reason on any refusal.
- 2
Check the status
If the header says Paused, start the bot. If it holds a position, read the closing-a-position page first.
- 3
Check the broker
A Broker disconnected notice means no orders, exits included. Go to Integrations and select Reconnect.
- 4
Check the budget and tickers
If one unit costs more than Budget per entry, raise it. If the alert's ticker isn't selected on the bot, add it under Edit bot.
- 5
Check that the alert arrived
No row on the strategy's Logs tab means nothing reached Nyria. Check that the strategy is Active, then the alert source.
The seven states
- The bot is paused and acts on nothing.
- The broker connection expired. Charles Schwab ends each sign-in after 7 days.
- The budget per entry cannot buy one share, contract or coin.
- The ticker filter skips the strategy's alerts. The filter is on the bot.
- The strategy no longer runs on the bot's account type.
- The strategy's rules refused the alert before any bot saw it.
- The strategy has not fired, so no alert arrived.
Refusals that place nothing
- An entry outside the strategy's trading hours is dropped, not queued. Exits still run.
- A second entry is refused while Allow multiple entries is off and a position is open.
- Options alerts are refused while the options market is closed.
- A delta or quote that can't be found ends in an ALERT FAILED row. Nothing is ordered.
When a notice shows
- A notice needs a repeat: three identical refusals in a row, or two skipped alerts in 7 days.
- A paused bot, or a strategy that never fired, has no refusals to count.
Questions
- Does pausing a bot close its positions?
- No. Pausing closes nothing, and the bot ignores exit alerts while it is paused. Close the position at your broker, or start the bot before the exit alert is sent.
- Does Nyria retry a refused order?
- No. A refused entry or exit is logged and not sent again. The one exception is a close on a cash account that the broker rejected for a reason that clears by itself. Nyria re-sends that close once.
- Why is there no notice on my bot?
- A notice needs a repeat. A bot that is paused, or whose strategy never fired, has no refusals to count. Use the Logs tab.
- What should I quote to support?
- The reason_code in the refusal row's Raw JSON, the bot's name and the time of the row.
- What does it cost?
- Paper is free. Live trading from $15 a month.
Next
- Paste an alert into the alert tester to see how Nyria reads it.
- Step by step for one account: how to automate TradingView to Alpaca.
- Step by step for one account: how to automate TradingView to tastytrade.
- Alert tester.
Guides
What happens to my open position if I pause or delete a trading bot?
Pause closes nothing. Delete with a position open makes the bot Closing only.
Read guideWhy was my trading bot's exit skipped?
Skipped exits send nothing. Five causes, one leaves a position open.
Read guideWhy did my Telegram trade alert place no entry?
Over a minute late, no new entry. A close still runs. Post it again.
Read guideWhy does my trading webhook answer 200 but place no order?
A 200 can mean rejected or duplicate. The Logs tab names the reason.
Read guideWhy did my broker reject an automated order?
The broker's reason, and the fix for each common rejection.
Read guideTry a paper bot first
No card required. Paper is free. Live trading from $15 a month.