Open the channel's activity log first. It shows the raw message, what the parser extracted and the reason a signal was skipped. That distinction — message arrived vs signal created — narrows the problem immediately.
1. A keyword filter dropped it
A require-list that no message matches is the single most common cause of a channel going quiet. Clear the require-list and re-test.
2. The message is not a signal
Recaps, screenshots, "good morning" — the parser skips messages with no instrument or no direction. That is working as intended.
3. Confidence below your threshold
Ambiguous numbers, two setups in one message or heavy formatting lower the confidence score. Below your threshold, the signal is held for manual approval rather than executed. Check the approval queue before assuming it vanished.
4. Required fields missing
No stop-loss means no position, by default. The log names the missing field.
Still nothing in the log
Then the message never reached PipSync: the bot was removed from the channel, or the source is toggled inactive. Check both.