Troubleshooting

If your automated trades are not working as expected, use this guide to diagnose and resolve common issues.

Alerts Not Being Received

Symptom	Cause	Solution
No webhook entries in the activity log	TradingView alert not firing or webhook URL incorrect	Verify the webhook URL in your TradingView alert settings matches the Capital.com webhook URL shown on your Settings page (not the Alpaca URL).
No webhook entries in the activity log	TradingView alert expired	TradingView alerts have expiration dates. Check that your alert is still active and set to "Open-ended" if available.
No webhook entries in the activity log	Alert message format incorrect	The message field must be exactly `{{strategy.order.alert_message}}`. Any other text will cause the payload to be malformed.

Symptom	Cause	Solution
Log shows "Signal skipped -- no subscription"	No active SignalPipe or vyn premium subscription	Subscribe at app.blockresearch.ai to enable automated execution.
Log shows "Signal skipped -- automation disabled"	Automation is toggled off or Capital.com not connected	Go to Settings and enable Automation. Make sure Capital.com is connected.
Log shows "Signal skipped -- max deals reached"	All deal slots are occupied	Wait for an existing deal to close, or increase your Max Active Deals limit in Settings.
Log shows "Buy signal skipped -- new deals paused"	Accept New Deals is toggled off	Go to Settings and enable Accept New Deals.
Log shows "Unauthorized"	Pointer mismatch	Verify the pointer in your Pine Script settings matches the SignalPipe Secret shown on your Settings page.

Symptom	Cause	Solution
Log shows "Session creation failed"	Capital.com credentials are invalid or expired	Reconnect your Capital.com account in Settings with fresh credentials.
Log shows "Position open failed"	The instrument is not available or the market is closed	Check if the instrument is tradable on Capital.com. Some instruments have limited trading hours.
Log shows "Invalid size"	Size is 0 or not a valid number	Check your Pine Script settings. The position size calculation must produce a number greater than 0.
Log shows "Order rejected by Capital.com"	Insufficient margin or account restrictions	Check your Capital.com account for available funds and any trading restrictions.

Symptom	Cause	Solution
Log shows "Take-profit set failed"	TP level could not be set on the position	The position is open but unprotected. Use the "Edit TP" action on the deal card to retry, or set a TP manually on Capital.com.
TP never hits	TP price set too high	Lower your Take-Profit Percentage in Settings. A lower TP% means the target is closer to your entry price and more likely to be reached.

Symptom	Cause	Solution
Dashboard shows "not connected"	Credentials invalid or session expired	Reconnect your Capital.com account in Settings.
Active deal shows but no position on Capital.com	TP was hit or position was manually closed	Reload the dashboard to trigger a sync.
P&L shows as $0 or incorrect	Live position data could not be fetched	Check your internet connection and Capital.com API status.

Always check the Log tab first. Every action SignalPipe takes is logged with a descriptive message.
Use the Test tab. Send manual test orders to verify your setup without waiting for a real signal.
Start with demo mode. Verify everything works with virtual money before switching to live trading.
Make sure you use the correct webhook URL. Capital.com uses a different webhook endpoint than Alpaca. Check the URL on your Capital.com Settings page.
One alert per chart. Having multiple alerts for the same strategy on the same chart can cause duplicate signals.
Keep your TradingView session active. Alerts only fire while your TradingView session is running. A paid TradingView plan ensures server-side alert execution.