Strategy Field

Reject entry if signal is older than

The Reject entry if signal is older than setting applies only to the proposed entry order when too much time has passed since the effective reference time plus any configured Delay, measured in seconds. The reference time is the optional time field in your webhook JSON when you send it (for example the bar or alert time from TradingView); if you omit time, TradersPost uses when the webhook was received. The number you configure is the maximum allowed seconds from that reference (after delay) before the entry is ignored. TradersPost evaluates this after it has already communicated with your broker to gather the data needed to compute the planned entry (for example quotes and positions); if the signal is too old at that step, the entry is not included in the trade plan. Including an accurate time helps when TradingView or another hop delivers the HTTP request late but the payload still reflects when the signal actually occurred.

This check does not cancel open-order cancellations and does not apply to exit planning. A trade is only fully rejected when there are no open orders to cancel, the exit order is not planned (for example it was ignored because the exit signal was too old), and the entry order is not planned (for example because entry staleness was exceeded, or because entry requires an exit that was not planned).

The value must be a whole number of seconds between 1 and 30. Leave blank to disable this check for entries.

The exit setting (Reject exit if signal is older than) is separate: setting one does not set the other, and the entry setting does not apply when planning an exit.

Webhook time (optional reference clock)

When you include time in the JSON, the staleness check uses that moment (plus any configured Delay) as the start of the clock, instead of when TradersPost received the webhook. That measures roughly when TradingView (or your system) considers the alert to have fired → when the trade plan is ready after broker calls, even if the HTTP delivery was slow.

Example: rejectAfter (or your strategy’s Reject entry if signal is older than value) is 10 seconds. The alert really fired at 10:00:00 and your payload sends that as time, but the webhook only reaches TradersPost at 10:00:45. Broker planning then finishes quickly at 10:00:46. Because the reference time is 10:00:00, the signal is already about 46 seconds old, so the proposed entry is not kept in the trade plan even though work after receipt was fast. Without time, the same payload would anchor to receive time (10:00:45) and would likely not be excluded for age.

time may be any string PHP can parse as a date and time (for example 2026-04-23 10:00:00 or ISO-8601). In TradingView, map a time placeholder into your alert JSON so time reflects the bar or alert time.

{
    "ticker": "SPY",
    "action": "buy",
    "orderType": "market",
    "time": "2026-04-23 10:00:00",
    "rejectAfter": 10
}

Webhook rejectAfter (entry)

Payloads may include rejectAfter for a per-signal maximum signal age in seconds. The effective entry value comes from the webhook when either:

  • Allow signal overrides is enabled on the strategy or subscription, or
  • Allow signal override is enabled for Reject entry if signal is older than

If signal values are allowed for this field and the payload includes rejectAfter, that value is used. If signal values are allowed but the payload omits rejectAfter, the configured Reject entry if signal is older than value in the strategy or subscription is used.

If neither Allow signal overrides nor Allow signal override for Reject entry if signal is older than is enabled, rejectAfter in the webhook is ignored for entry planning and only the configured value applies.

Example webhook payloads

Entry using only the strategy's configured value (no per-signal rejectAfter):

{
    "ticker": "AAPL",
    "action": "buy",
    "orderType": "limit",
    "limitPrice": 150
}

Entry with a per-signal rejectAfter (requires Allow signal overrides and/or Allow signal override for Reject entry if signal is older than as above):

{
    "ticker": "AAPL",
    "action": "buy",
    "orderType": "limit",
    "limitPrice": 150,
    "rejectAfter": 5
}

Start trading at scale today. Sign up for free.

Free 7-day trial

Set-up in 3 minutes

Paper account for testing

TradersPost operates as a non-custodial automated trading platform, enabling users to connect alerts from their preferred trading platforms to their selected brokerage or exchange accounts. It abstains from the transmission, custody, or management of customer funds, covering both traditional and cryptocurrency assets. Typically, registration requirements set by regulatory entities such as the SEC, FINRA, or FinCEN apply to entities that hold or transmit customer funds. To ensure ongoing compliance, TradersPost regularly engages with regulatory authorities to confirm its adherence to all relevant local and federal laws.

TradersPost does not provide alerts, signals, research, analysis, or trading advice of any kind. It is designed to assist traders and investors in making their own trading decisions based on their alerts. The platform does not offer recommendations regarding securities to buy or sell, nor does it provide trading or investing advice. The platform and its features, capabilities, and tools are provided 'as-is' without any warranty.

Risk Disclosure: The use of automated trading systems involves inherent risks, including the potential for significant financial loss. These systems operate based on predetermined algorithms that may not fully adapt to changing market conditions, possibly making them unsuitable for some investors. Individuals are advised to thoroughly assess their financial situation and risk tolerance before using this platform.

Testimonials appearing on this website may not be representative of other clients or customers and is not a guarantee of future performance or success.

© 2026 TradersPost, Inc. All rights reserved.