No Exit Reject After Exceeded

This message means TradersPost rejected the proposed exit order for this signal because the signal was treated as too stale at the moment the check ran: more time had passed since the effective reference time (plus any Delay) than your configured maximum allows.

The reference time is either the time value in your webhook JSON when you include it (for example when TradingView or your strategy fired the alert), or when TradersPost received the webhook if time is omitted. Any Delay configured on the strategy or subscription is added to that reference before measuring elapsed seconds. The check runs after TradersPost has already communicated with your broker to gather the data needed to compute the proposed exit (for example quotes and position details). Right after that planning step, TradersPost compares elapsed time to your limit. If elapsed time is greater than the limit, the proposed exit is not kept in the trade plan and you see this message instead of an exit order ready for execution. This often appears when delivery is slow but you can reduce false rejects by sending an accurate time in the payload so staleness is judged from when the signal actually occurred, not only when the HTTP request arrived.

The limit comes from Reject exit if signal is older than on your strategy or subscription, and/or the rejectAfter field on the webhook when Allow signal overrides and/or Allow signal override for that setting permits it. See Reject exit if signal is older than and Allow signal exit reject after for details and examples.

The entry staleness check is separate (Reject entry if signal is older than); tightening the entry limit does not change exit behavior, and this message is only about the exit leg of the trade plan.

If you expect occasional delays, raise the seconds value (still between 1 and 30) or leave the field blank to disable the check. If signals should always be fresh, investigate why they arrive late (alert timing, webhook retries, clock skew, or heavy Delay usage).