What the parser looks for
Common fields include symbol, buy or sell direction, entry area, stop loss, take-profit levels, and updates such as close or move stop loss.
Parsing is not execution
A parsed signal still needs to pass the user's rules. This keeps parsing separate from the decision to copy a trade.
Why visibility matters
When a message is unclear or skipped, the user should be able to review what happened instead of guessing why a trade did not open.
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.