Skip to main content

​
Why Did Mirrorpip Not Execute My Trade triggered from Tradingview? Complete Troubleshooting Guide

One of the most common questions traders ask when setting up TradingView automation is:
“My TradingView alert triggered successfully, but Mirrorpip did not place any trade. Why?”
In most cases, the issue is caused by a configuration error rather than a system problem. This guide covers the most common reasons why Mirrorpip may not execute a trade and how you can quickly diagnose and fix the issue.

​
Understanding the Trade Execution Process

Before troubleshooting, it’s important to understand how a trade reaches your exchange account. 
TradingView Indicator
        ↓
TradingView Alert Triggered
        ↓
TradingView Message (JSON)
        ↓
Webhook Sent to Mirrorpip
        ↓
Mirrorpip Validates Data
        ↓
Mirrorpip Sends Order
        ↓
Exchange Executes Trade
A failure at any step can prevent trade execution. The good news is that most issues can be fixed in just a few minutes.

​
Quick Checklist

Before diving into detailed troubleshooting, verify the following: ✅ TradingView alert triggered ✅ Webhook URL is configured ✅ JSON message is valid ✅ Symbol exists in Mirrorpip watchlist ✅ Exchange account is connected ✅ Sufficient margin is available ✅ Correct order type is being used If everything appears correct, continue reading.

​
Reason 1: Symbol is Not Added to Mirrorpip Watchlist

This is the most common reason for failed executions. Mirrorpip can only process symbols that exist inside your configured watchlist. For example: Your TradingView chart: 
BTCUSDT
TradingView Alert: 
BTCUSDT Buy Signal
But if BTCUSDT has not been added to your Mirrorpip watchlist: ❌ Alert triggers ❌ Webhook reaches Mirrorpip ❌ Order is rejected ❌ No trade is executed

​
How to Fix

Navigate to your Mirrorpip dashboard and verify that the symbol exists in your watchlist. Example: 
Watchlist
├── BTCUSDT
├── ETHUSDT
├── SOLUSDT
If the symbol is missing, add it and test the alert again.

​
Reason 2: Invalid JSON Message

Mirrorpip relies on the TradingView Message field to understand your trading instructions. If the JSON is malformed, Mirrorpip cannot process the alert.

​
Example of Valid JSON

[
  {
    "exchange":"coinswitch",
    "price":"{{close}}",
    "chart_symbol":"{{ticker}}",
    "order_type":"buy",
    "quantity":"100$",
    "tp":"10%",
    "sl":"5%",
    "code":"68ZMEQ6S5ZA507N0"
  }
]

​
Example of Invalid JSON

[
  {
    "exchange":"coinswitch"
    "price":"{{close}}",
    "chart_symbol":"{{ticker}}"
  }
]
Notice the missing comma after: 
"exchange":"coinswitch"
This small mistake can cause the entire alert to fail.

​
Common JSON Errors

​
Missing Commas

"exchange":"coinswitch"
"price":"{{close}}"

​
Missing Quotation Marks

"quantity":100$

​
Missing Brackets

{
 "exchange":"coinswitch"

​
Extra Characters

buy btc now
inside the JSON payload.

​
How to Fix

Always copy the JSON directly from: 
Mirrorpip
→ Profile
→ TradingView Automation Bot
→ Copy TradingView Conditional Alert Data
Avoid manually editing the JSON unless necessary.

​
Reason 3: Incorrect Exchange Name

The exchange field tells Mirrorpip where to place the order. Example: 
"exchange":"coinswitch"
If the exchange name is incorrect or unsupported, Mirrorpip cannot route the order.

​
Correct Examples

"exchange":"coinswitch"

"exchange":"delta"

"exchange":"bybit"

​
Incorrect Examples

"exchange":"coin switch"

"exchange":"deltaexchange"

"exchange":"by bit"
Even a small spelling error can prevent execution.

​
How to Fix

Generate fresh JSON from Mirrorpip instead of manually typing exchange names.

​
Reason 4: Webhook URL is Missing

Many users correctly configure alerts and JSON but forget to enable the webhook. Without a webhook, TradingView cannot send data to Mirrorpip.

​
What Happens Without a Webhook?

TradingView Alert
        ↓
Notification Sent
        ↓
User Receives Alert
Mirrorpip never receives the signal.

​
Correct Webhook URL

https://trade.mirrorpip.com/tradingview

​
How to Verify

Open the TradingView Alert. Navigate to: 
Notifications
→ Webhook URL
Verify the webhook URL is enabled and matches exactly: 
https://trade.mirrorpip.com/tradingview

​
Reason 5: Wrong Order Type

Mirrorpip supports multiple order actions. Examples:
ActionOrder Type
Open Longbuy
Close Longsell
Open Shortshort
Close Shortcover

​
Example

Suppose your strategy generates a short entry. Incorrect: 
"order_type":"buy"
Correct: 
"order_type":"short"
Using the wrong order type can cause unexpected behavior or rejected trades.

​
Reason 6: Insufficient Margin or Funds

Sometimes the alert reaches Mirrorpip successfully, but the exchange rejects the order. Common reasons include:
  • Insufficient balance
  • Margin unavailable
  • Leverage restrictions
  • Position limits exceeded

​
Example

Your JSON: 
"quantity":"1000$"
Available balance: 
$100
Exchange rejects the order. Mirrorpip cannot force execution when the exchange refuses the trade.

​
How to Fix

Verify:
  • Available balance
  • Margin availability
  • Leverage settings
  • Position sizing
on your exchange account.

​
Reason 7: TradingView Alert Never Triggered

Sometimes traders assume the alert triggered when it actually didn’t. Common reasons:
  • Condition never became true
  • Alert expired
  • Wrong trigger configuration
  • Alert disabled

​
Verify Alert Logs

In TradingView: 
Alerts
→ Alert Log
Check whether the alert actually triggered. If there is no entry in the alert log, Mirrorpip never received a signal.

​
Reason 8: Expired TradingView Alert

TradingView alerts have expiration dates. Example: 
Expires in 30 Days
Once expired: ❌ No alerts generated ❌ No webhook sent ❌ No trades executed

​
How to Fix

Review: 
Alert
→ Expiration
and create a new alert if needed.

​
Reason 9: Wrong Symbol Mapping

Your chart symbol and watchlist symbol must match. Example: TradingView: 
BTCUSDT
Mirrorpip Watchlist: 
BTCUSD
These are different instruments. Mirrorpip may reject the trade because it cannot find the symbol.

​
How to Fix

Ensure the TradingView chart symbol exactly matches the symbol configured inside Mirrorpip.

​
Reason 10: Using a Free TradingView Plan

Webhook functionality requires a paid TradingView subscription. Without webhook access: ✅ Alerts can trigger ❌ Alerts cannot reach Mirrorpip ❌ Automation cannot occur

​
How to Verify

Open your alert settings. If the Webhook URL field is unavailable, your TradingView plan does not support webhooks.

​
Step-by-Step Troubleshooting Process

Whenever a trade fails to execute, follow this sequence:

​
Step 1

Did TradingView alert trigger? If No:
  • Check alert condition
  • Check expiration
  • Check trigger type

​
Step 2

Is Webhook URL configured? If No: 
https://trade.mirrorpip.com/tradingview
must be added.

​
Step 3

Is JSON valid? If No: Generate fresh JSON from Mirrorpip.

​
Step 4

Is Symbol in Watchlist? If No: Add symbol to watchlist.

​
Step 5

Is Exchange Connected? If No: Reconnect your exchange account.

​
Step 6

Is Margin Available? If No: Add funds or reduce quantity.

​
Most Common Causes Ranked

Based on actual user support tickets, the most common causes are:

​
#1 Symbol Not in Watchlist

Most frequent issue.

​
#2 Invalid JSON

Usually caused by manual edits.

​
#3 Missing Webhook URL

Very common among new users.

​
#4 Insufficient Margin

Especially on futures exchanges.

​
#5 Wrong Exchange Configuration

Incorrect exchange names or disconnected accounts.

​
Final Thoughts

If Mirrorpip did not execute your trade, the problem is usually one of four things:
  1. Symbol not added to watchlist
  2. Invalid JSON message
  3. Incorrect exchange configuration
  4. Missing or incorrect webhook URL
By systematically checking each step in the automation flow, you can identify and resolve nearly all execution issues within minutes. Remember: 
TradingView Alert Triggered
≠
Trade Executed
For successful automation, every component of the workflow must be configured correctly: Alert → Message → Webhook → Mirrorpip → Exchange Once these components are properly connected, Mirrorpip can execute your TradingView signals automatically and reliably across supported exchanges.