Skip to content

Signal History

The Signals page of the dashboard lists every alert that reached one of your licenses, newest first, with what happened to it. Open it after your first alerts and whenever a trade you expected is missing.

Reading the list

Each row is one signal:

  • Time when our servers received the alert. Times are shown in your browser's time zone (the page says which); if your browser blocks JavaScript they are shown in UTC.
  • Signal: the command and the symbol. A Test badge marks a test signal, a Retry badge a signal you sent again.
  • Status: see the table below.
  • Price and Ticket: the entry price and the MetaTrader ticket of an executed order.
  • Message: the reason, when something went wrong.
  • Command: click it to see the exact line the EA received, including the signal id our servers added (sig=).

Above the list, the EA of this license box shows whether the EA is connected right now (see EA status).

Filters

  • License: the history shows one license at a time. By default, the one with the most recent signal.
  • Status: one status only. The coloured badges above the list show how many signals have each status; click one to filter by it.
  • Period: last 24 hours, 7 days, 30 days, or all time.
  • Symbol: any part of the symbol name, for example EUR.

Clear removes the filters. The list shows 50 signals per page.

Statuses

Status What it means and what to do
Executed Your EA reported that the command was carried out. For a pending order this means the order was placed, not filled. For a close command it also appears when there was nothing to close.
Delivered The signal reached your EA and we are waiting for its answer. It changes within seconds.
No response The signal was sent to your EA, but it did not answer within 30 seconds. The order may or may not have been placed: check MetaTrader before doing anything. If the EA answers later, the status is updated.
No reply Sent to your EA, but no answer was ever recorded. Mostly seen on older signals. Treat it like No response.
Not delivered No EA was connected for this license when the alert arrived, so nothing was executed. The signal is not kept for later. Check that MetaTrader is running with the EA attached (see Troubleshooting).
Rejected Our servers refused the alert before it reached your EA, for example because it has fewer than three fields or a pending order has no entry=. The reason is in the message. Fix the alert in TradingView.
Error Your EA tried and MetaTrader or the broker refused, or our servers could not send it. The reason is in the message; the common ones are explained in Troubleshooting.

The status filter also lists Scheduled and Market closed. Pine2Trade does not hold or schedule signals today, so no signal gets these statuses: an alert that arrives while the market is closed is sent to the EA at once and ends as Error (MARKET_CLOSED).

Pine2Trade never re-sends a signal by itself. A signal that was not executed stays that way unless you send it again with Retry now.

For cancel commands, the Ticket and Price columns do not describe an order: ignore them.

Retry now

Signals with the status Error, Not delivered, No response or No reply have a Retry now button. It sends the same command to your license again, exactly as TradingView would.

  1. Click Retry now. A confirmation page shows the exact command that will be sent and when the original alert arrived.
  2. Read the warning, then click Send again now.
  3. A few seconds later the result appears in the list as a new signal with a Retry badge. The original row shows Retried at with the result and a See the retry link.

A retry trades at today's price

A retried buy or sell opens a new position at the current market price, which may be far from the price when the alert fired. A retried pending order is placed entry= pips from the current price. Before retrying a signal with No response or No reply, check your open positions in MetaTrader: the original may have been executed, and a retry would open a second position.

A retried close command closes at the current price; if there is nothing left to close, it simply reports that. A retried cancel command cancels the pending orders that still exist.

Good to know:

  • If the retry fails too, the original row offers Retry again. A retry itself cannot be retried.
  • The same signal can be sent again once a minute at most, so a double click cannot send it twice.
  • Not available for test signals, for licenses that have expired (renew first) and for group licenses.
  • If the dashboard says that the signal service did not answer in time, the retry may or may not have been sent: wait a minute and look at the list before trying again.
  • Telegram marks the messages about a retried signal with "(retry)".