The signal was not recognized: why
A post with levels came out in the channel, but there is no trade and no notifications either. First you need to work out which of the two cases is yours: the bot did not parse the post as a signal, or it did parse it but did not open a trade for you specifically.
How to tell them apart
| Sign | The signal was not recognized | The signal was recognized but did not pass your filters |
|---|---|---|
| Buttons under the post | None | Present: 👁 View signal, 📈 Open signal, ⚡ Enable auto-trading |
| Your notifications | Silence | “⚠️ Signal not processed · Channel: «…» · Bot: «…» · Reason: …” |
| Who learns the reason | The channel owner — by a private message from the bot | You — in the notification |
| Other subscribers | Nobody has a trade | Some opened, some did not |
One reservation: the buttons appear only if the main bot has the "Edit messages" permission in the channel. Without it, signals are processed but there are no buttons — then rely on the notifications and on whether others got a trade.
The second case is covered in What happens after a signal is published. What follows is about the first case.
Why the bot did not accept the post
The bot does not send the reason to subscribers — the channel owner receives it: “⚠️ Post … in channel "…" was not accepted as a signal — no trades were opened. Reason: … Fix the text and publish the signal again.” The most frequent reasons:
| What is in the post | Why it did not work |
|---|---|
| The signal is a caption under a picture | Only a text post is read; such posts are skipped silently |
| No stop line | The stop is required: “Value not found for STOP_LOSS” |
| Two stops | “…do not support multiple Stop-Loss orders in a single trade” |
| A short without leverage | Spot allows LONG only: “Leverage not specified, signal recognized as SPOT (only LONG available)” |
| Stop and target on the same side of the entry | “Direction conflict…” |
| The pair is not on Bybit, or a typo | “Pair … is not traded on …” |
A second hashtag (#scalp, #signal) | The bot takes the hashtag for the pair |
Two headings for one block (TP: and Take profit:) | “More than one keyword found for …” |
| Leverage outside the range or written as a word | “Leverage cannot exceed 999”, “Failed to parse leverage value” |
| Signal processing paused by the channel admin | Posts are not processed at all |
| The post was edited after publishing | Edits are not re-read — a new post or an admin command is needed |
There is also a treacherous case without any error: targets on one line separated by / (the bot takes only the first one), or a number with no separator (TP1 87 000 turns into 187 000). The signal is recognized, but not the way the author intended — you can see this in the card behind the 👁 View signal button.
What a subscriber should do
- Make sure there are no buttons under the post and your notifications are silent.
- Tell the channel admin: the bot has sent them the reason, and the full format is described in Signal format: full specification.
- Wait for a corrected post — editing the old one will not help, a new one is needed.
- If the trade has to be opened for a post that is already out and the signal is still not recognized, the only way is by hand: Main menu → 🕹️ Manual Trading (see Manual trading).
If the bot is silent on every post of the channel in a row, the format is probably not the problem: check whether the bot is connected to the channel and whether auto-trade is on — The bot is silent after connecting a channel.
Typical mistakes and what the bot says
- Nothing — a subscriber gets no notification for an unrecognized post; that is the main sign.
- “Signal not found or the link has expired.” — you pressed a button under a very old post.
- “The channel is currently off — its signals are not processed.” — the channel admin has paused signal processing.
- “⚠️ Signal not processed …” — here the signal was in fact recognized; the reason in the message concerns your settings, not the text of the post.