Signal parsing
Guide contents
  1. What the parser looks for
  2. Parsing is not execution
  3. Why visibility matters
  4. Read the fields before the outcome
  5. Handle ambiguity and updates safely

What the parser looks for

Check the fields Tragram extracted from the message—such as symbol, direction, entry, stop loss and targets—against the original Telegram text. If a value is missing or misread, do not assume the parser filled it in correctly.

Parsing is not execution

A parsed signal still needs to pass channel settings and account checks. Tragram does not provide a per-signal manual approval step; configure and test the channel before enabling entries.

Why visibility matters

Use the signal status and execution history to distinguish an unrecognized message, a channel-rule skip and a broker rejection. They are different stages and need different fixes.

Read the fields before the outcome

An illustrative message might contain BUY, a broker instrument, an entry, SL and TP values. Check how each field was interpreted. Commentary, performance recaps and incomplete instructions should not be assumed to be executable entries. Do not invent a missing direction or instrument to make a message fit.

Handle ambiguity and updates safely

A reply or edit needs a resolvable original target before it can affect an existing trade. Compare the message context and displayed status. If interpretation is unclear, retain the message reference and contact support; avoid repeatedly resubmitting it and creating uncertainty about duplicates.

Related guides

Next step

See the product page connected to this guide and review how the workflow works inside Tragram.