Appearance
Are you an LLM? You can read better optimized documentation at /dashboard/signal-log.md for this page in Markdown format
Signal Log
The Signal Log records every signal that TTMT has received from your connected Telegram channels. Whether a signal was executed successfully, rejected for safety reasons, or failed while TTMT read it -- it is all here.
This page is your go-to resource for understanding how TTMT read each message and what it did with it.
Signal Table
Each row represents a single signal event:
| Column | Description |
|---|---|
| Channel | The Telegram channel that sent the signal |
| Raw Text | The original message text (truncated in the table, full text in details) |
| What TTMT Read | Summary of the fields TTMT pulled out: symbol, direction, entry, SL, TPs |
| Status | Processing outcome (see status reference below) |
| Received | Timestamp when the signal was picked up |
| Processed | Timestamp when processing completed |
Each signal carries a reference ID (sig_…) you can use to find it later or quote it in a support request.
Signal Statuses
Signals pass through multiple stages. The status badge tells you exactly what happened to a signal:
Active Processing States
| Status | Meaning |
|---|---|
pending | Signal received, waiting to be processed |
queued | In line to be processed |
parsing | Currently being analyzed by TTMT |
executing | Read successfully, trade execution in progress |
execution_paused | Execution temporarily paused (e.g., safety limit reached) |
Completed States
| Status | Meaning |
|---|---|
executed | Trade successfully placed from this signal |
executed_awaiting_modification | Trade placed, waiting for followup details to modify |
executed_via_followup | Trade was originally an alert, then completed by a followup message |
pending_followup | Alert signal received, waiting for the followup with full details |
Terminal States
| Status | Meaning |
|---|---|
failed | Processing failed -- see error details for the reason |
delivery_failed | Signal was received but could not be sent for trade execution |
rejected | Signal was valid but rejected by safety checks (e.g., duplicate, stop loss on wrong side) |
ignored | Signal was intentionally skipped (e.g., symbol not in your filter, channel paused) |
skipped | Signal was deprioritized or superseded by a newer signal |
Most Signals Should Be "Executed" or "Ignored"
If you see a lot of failed or rejected signals, it is worth investigating. Failed signals may point to a connection issue or a channel that sends poorly formatted messages. Rejected signals are usually the safety systems doing their job -- but a high rejection rate might mean you need to adjust your channel settings. A rejected signal often corresponds to a Rejected trade outcome chip with a specific reason (invalid stops, market closed, and so on), and the trade detail names it -- see Trade Log.
Expandable Signal Details
Click any signal row to see the full breakdown:
- Raw signal text -- The complete, untruncated message from Telegram
- What TTMT read -- Every field TTMT pulled from the message: symbol, direction, entry price, entry zone, stop loss, take profit levels (TP1 through TP6)
- Validation results -- Which safety checks passed and which flagged issues (stop loss check, take profit check, entry zone check, duplicate signal check)
- Execution result -- If a trade was placed, links to the trade record with order details, plus the linked trade's outcome chip, so you can see at a glance how the trade that came from this signal ended. See Trade Log for what each chip means.
- Error details -- If the signal failed or was rejected, the specific reason it failed
Filters
Narrow the signal log with:
- Date range -- Focus on a specific time window
- Channel -- See signals from a particular channel only
- Status -- Show only executed, failed, rejected, or any other status
Debugging Channel Performance
Combine the channel filter with the status filter to quickly assess a channel's signal quality. If a channel produces a high ratio of rejected or failed signals compared to executed, it may be worth reconsidering whether to keep following it.
Signals in terminal states (executed, failed, rejected, ignored, skipped) can be soft-deleted from this table using Cleanup mode and restored later -- see Trash & Restore.
Alert-then-details signals
Some channels post an alert first (just the direction and symbol), then follow up with the full details (entry, SL, TPs) in a separate message. This is a channel's signaling pattern, not a TTMT setting.
When this happens, you will see:
- A signal with status
pending_followup-- the initial alert - A second signal with status
executed_via_followup-- the completed trade after the details arrived
How TTMT handles it is controlled by the channel's execution mode. Channels set to execute_on_alert will execute immediately on the first message and apply the followup as a modification. Channels set to complete_only will wait for the full details before executing.
Related Pages
- Trade Log -- See the trades that resulted from these signals
- Signal Tester -- Test how TTMT would read a signal without real money
- Trash & Restore -- Restore soft-deleted signals
- Channel Management -- Configure channel settings and execution modes
- Signal Processing -- How signals flow through the system