Why was my exit skipped?
What a Skipped exit row means on a bot or strategy log: no position, a rejected or canceled entry, a wrong side, or a failed exit left open.
A skipped exit sends nothing to your broker and is not retried. The row on the Logs tab names which of five things happened, and each has its own fix. The first four leave nothing open on that bot. The last one leaves a position open, and that one needs you.
Open the row for its details. The bot's rows are under My bots; the strategy's rows are on the strategy's Logs tab, which only the strategy's owner can read.
The bot holds no position
The bot's log shows a Skipped row whose raw line ends No position found, with the reason No open NVDA position for this bot. in its details. Its reason code is no_position.
The strategy tracked a position, so it sent the exit to every bot, but this bot had none to close. The usual causes:
- The entry never filled on this bot, or was closed at the broker by hand.
- An earlier exit already closed it.
Nothing is open on the bot, so there is nothing to fix. The notification reads NVDA exit skipped, no open position. The strategy owner's row for the same alert counts only the bots that had something to send, and names the rest under Bot results as Nothing to close.
The entry was rejected
The raw line also ends No position found, and the reason reads No position: the entry was rejected. Its reason code is entry_rejected.
The entry before this exit was refused, so the exit was expected to find nothing. Scroll up to the entry's row: it names the cause, such as a budget below one contract or a broker rejection, and why is my bot not trading? has the fix for each. This row does not count toward a failure notice, because the rejection was already reported.
The exit arrived before the entry filled
The raw line reads like SELL SPY | Entry order 40472068 cancelled (no position to close), with the reason The exit alert found no open position, so the pending entry order was canceled. Its reason code is entry_cancelled.
The entry order was still working at the broker when the exit came in. Rather than close a position that did not exist, Nyria canceled the entry. Nothing opened and nothing closed. The notification is titled SPY entry canceled before it filled and reads The exit alert arrived first.
On the strategy's log, the same alert shows as 2 of 2 entries canceled.
This happens with limit entries that sit unfilled, and with exits that follow entries by seconds. If you want the entry to fill, give it longer before the exit, or use a market order for the entry.
The exit named the wrong side
These rows are on the strategy's log, because the strategy refused the exit before any bot saw it.
| Raw line ends | What it means |
|---|---|
Rejected: no open long SPY position to close | The strategy tracks no long SPY position. An earlier exit closed it, the entry was refused, or the exit names a ticker the entry did not |
Rejected: no open short SOLUSDT position to close, only a long one | The exit says short, and the open position is long. Send the exit for the side that is open |
Rejected: no open long SPY position to close, and this strategy has no active bots | No position, and no bot on the strategy is active to hold one |
A strategy whose Short behavior is set to Do nothing refuses short entries with Rejected: short entries are disabled (Short behavior is set to Do nothing), so a later short exit also finds nothing. Set the behavior under trading behavior.
The exit failed and the position is still open
The bot's log shows a row badged Needs attention that reads like SPY 770C exit failed at Tradier 14 minutes ago and the position is still open. Close it at Tradier. Its reason code is stranded_exit.
Nyria sent the close and the broker refused it, or never confirmed it, and Nyria does not retry. The position is open at your broker right now. Close it there, or fix what the broker refused and send another exit alert. Closing a position covers both.
The bot's page shows a notice headed Exit failed, position still open:
Nyria won't retry. Close the position at Tradier.
Its button is View log. The notice appears after three failed exits in a row and goes away after the bot's next successful order.
The notice on the bot
After three skipped exits in a row with no order in between, the bot's page shows a notice headed No position to exit:
Check the log for what happened to each entry.
Its button is View log. Exits skipped because the entry was rejected do not count toward it: the entry's own refusal is what is reported.
What to do
- Open the bot's Logs tab and read the newest row's details. Match its raw line to a section above.
- Open the positions page at your broker. If the position is open there and the bot says it holds none, close it at the broker, then pause the bot before the next alert.
- If nothing is open anywhere, nothing is left to do. The next entry alert starts a new position.
FAQ
Does a skipped exit leave anything open?
A row that ends No position found, or one that canceled a pending entry, leaves nothing open on that bot. A row that says the position is still open does, and that position is yours to close.
Why did the strategy say it sent the exit when my bot skipped it?
The strategy sends an exit to every bot that follows it. A bot whose entry never filled, or was closed at the broker by hand, has nothing to close and logs the skip. The strategy's row counts the bots that sent an order.
Will Nyria send the exit again later?
No. A skipped or failed exit is logged once. Send a new exit alert after the cause is fixed, or close at the broker.
Related
- Why is my bot not trading?: entries that place no order
- Closing a position: every way to get flat
- When an order fails: the three stages an alert passes through
- Troubleshooting: fixes listed by log message
- Trading behavior: long and short behavior, exits on each side
Why is my bot not trading?
Work through the six usual reasons a Nyria bot places no order: paused, disconnected broker, small budget, ticker filter, strategy rules, no alert.
What happens to an option that expires today?
What Nyria does in the last 30 minutes before the close for an option expiring that day: the bot log row and notification for each outcome.