Table of contents
- 1. Locate where signal bot orders stopped
- 2. Resolve unreadable Telegram instructions
- 3. Separate pending signal bot orders from rejections
- 4. Check quantity rules and spendable balance
- 5. Reconcile partial fills in signal bot orders
- 6. Escalate with the order record
To troubleshoot failed Telegram signal bot orders, first identify whether the instruction became a recognized signal, created a trade, reached the exchange, or filled only partly. Compare the original message, bot status, and exchange order history before changing settings. A channel target being reached does not establish that your account filled at that price (signal execution differences).
1. Locate where signal bot orders stopped
Cornix automates copying signals from Telegram signal groups to exchange accounts. Use the Signals Bots overview to understand which execution rules belong to the follower rather than the channel. That distinction helps separate an unreadable instruction from an account-specific execution issue.
Build a short incident record before editing anything. Save the original message and subsequent updates, the channel, symbol, destination account, spot or futures market, timestamp with time zone, exact notification, and any exchange order identifier. Keep screenshots free of credentials. Use these records to answer the following questions in order:
- No recognized signal: inspect message formatting and the intended market.
- Signal exists but no expected trade: compare destination account and personal configuration.
- Trade exists but an order is absent: inspect conditional placement rules.
- Order was rejected: follow its exact rejection message.
- Order partly filled: reconcile executed quantity and the remaining active order.
Treat this as a tracing sequence, rather than a reason to resend the message. Personal settings can override channel configuration, while exchange conditions determine actual execution.
2. Resolve unreadable Telegram instructions
When no recognized signal appears, compare the original text against the parsing rules. Look for a full pair, an entry keyword such as Buy or Entry, price-based targets, and Stop or SL before the stop price. Sell is a take-profit keyword, so using it for a stop changes the instruction's meaning (signal posting guide).
Keep the actionable message in structured plain text. Send an accompanying chart separately: attaching a picture to the same signal message prevents parsing. Review entries, targets, stop, and trailing formatting rather than assuming readable prose is executable (signal format guide).
Also compare the signal's market with the follower account. A spot instruction and a futures destination are different market choices; establish which market the message actually identifies. A long signal without explicit leverage or a named leveraged exchange usually becomes a spot signal, so a missing futures trade can originate in classification rather than exchange rejection.
Ask the channel administrator to resolve the source instruction when its intended market or stop is unclear. Keep the original message in your incident record so the correction can be compared with what the bot actually received.
3. Separate pending signal bot orders from rejections
An absent exchange order is not automatically a failure. Trailing entry and trailing take-profit instructions can remain pending until their trailing conditions activate. Take-profit orders are placed only after an entry fills. On spot exchanges, the platform dynamically allocates funds between take-profit and stop-loss orders according to price proximity (order placement rules).
Inspect the configured trigger before deciding that an order disappeared. The trailing orders overview provides context for following price with a conditional instruction. For exit coordination, read the stop-loss and take-profit guide before changing a pending order into an immediate instruction.
A rejection belongs to a different branch. The Rejected by Exchange status identifies an order canceled following an exchange rejection for an unknown reason. That label alone does not establish insufficient funds, a permission problem, or invalid size (exchange rejection status). Preserve any more specific exchange response and match its timestamp to the attempted order.
4. Check quantity rules and spendable balance
For Some Targets Have Invalid Quantities, inspect each submitted order rather than only the total trade allocation. This error concerns an order outside exchange quantity limits; inspect the stop as well as the individual entries. Market and limit orders can have different quantity requirements (invalid quantity explanation).
The relevant setting is Edit Signals Bot > Advanced Settings > Stop Type, where Market and Limit are available choices. Compare the applicable exchange rules before changing it. A different stop type changes execution behavior as well as the quantity rules that apply; it is not a universal repair for signal bot orders.
Distinguish account balance from funds available for the new instruction. For example, Kraken's Insufficient funds response directs users to inspect existing positions and orders that may be holding funds. Its separate errors identify minimum order volume and maximum open-order counts. These are different causes requiring different corrections, not interchangeable balance errors (exchange API error definitions).
Do not increase allocation merely to make an error disappear. First identify whether the failing component is an entry, an exit allocation, or the whole stop quantity. For broader execution-cost planning after resolving the incident, read the bot fees and slippage guide.
5. Reconcile partial fills in signal bot orders
A partial fill means some requested quantity executed while the whole order did not complete. Compare filled quantity, remaining quantity, execution prices, and current order status. Execution depends on available order-book volume: a channel target can be reached while an account order fills partly or remains unfilled. Exchange-specific prices and personal settings can also produce different results.
Record the remaining position separately from the unfilled order. Before replacing anything, determine whether the original remainder is still active and whether the proposed replacement concerns that remainder or the full original amount. Do not treat a channel completion message as an account execution receipt.
An incomplete entry can also affect exit placement. The Waiting for Entries status concerns an undersized take-profit during the buying stage, before any take-profit executes. Its allocation is redistributed to valid pending take-profits. Additional entry fills can make the target valid; once a take-profit is reached, remaining invalid targets are canceled as Not Enough Funds Invested (waiting-for-entries explanation).
This is why a missing exit target and a rejected entry should not receive the same response. Trace the funded amount and target status before changing the exit plan.
6. Escalate with the order record
Contact exchange support when you need an explanation of an exchange rejection, account restriction, or exchange execution record. Contact platform support when the recognized signal, configured trade, and observed placement cannot be reconciled with the documented behavior. Escalate an unexplained placement discrepancy with the relevant order record and the expected conditional behavior.
Send the incident record, exact error text, affected order identifiers, relevant settings, and the actions already taken. State the unresolved question precisely, such as whether the remaining quantity is active or why a specific target was rejected. Never include an API secret.
Before resuming, account for existing positions and resting orders, then change the identified cause rather than several settings together. For the next diagnostic branch, use the order troubleshooting resources.
Frequently Asked Questions
Why did an entry close with Sell Reached?
Sell Reached identifies remaining unfilled entries canceled when a take-profit is reached after another entry has filled. If no entry filled, cancellation depends on the configuration for closing before entry. This status is distinct from exchange rejection (order status definitions).
Does Merged mean a take-profit order failed?
Merged means a previous trailing order was still active when another target was reached. The new target's amount combines with that active trailing order rather than becoming a separate order.
Can API permissions prevent signal bot orders?
Yes. An API request can be denied when its key lacks permission for the requested task. Kraken distinguishes Permission denied from order errors such as insufficient funds, so inspect the exact response before changing allocation.
