Debug a Signal
When a deployed signal doesn't behave as expected, work through this page before contacting support and if you do need support, it tells you exactly what to send so you get a fast answer.
Common symptoms and first checks​
| Symptom | Check first |
|---|---|
| No trades at all | Is the strategy in Listening state (not paused)? Is your broker logged in today (NSE/BSE)? Did your entry condition actually become true? |
| Missed a trade you expected | Was the Max Concurrent / Max per Day limit already hit? Was the condition true on candle close, or only mid-candle? |
| Live results differ from backtest | Usually expected to a degree - see why results differ |
Check the execution for errors​
Open the execution on the Executions dashboard. A row in Error status has a View Error button; its detail page shows a red Error box with the time and the broker's message, plus a Messages Window with everything that happened. Copy the error text - support will need it.
Collect debug details​
If the checks above don't explain it, copy the signal's debug information:
Navigation: Signal → Signal Dashboard → Signals AI → Forward Test / Algo Trade → click the strategy → More → Debug (clicking copies the details to your clipboard)
Get help from inside the product​
The Help Center menu at the top of the Signals pages (Saved Signals, the builder, and Executions) has four entries:
| Entry | Use it for |
|---|---|
| Pinescripts Support | Opens a Telegram chat with an AlgoTest support executive for help with Pine Script |
| Customer support | Opens the AlgoTest support chat on Telegram |
| View Docs | Opens these docs |
| Video Tutorials | Step-by-step videos for Signals and Signals AI |
Contact support​
Send to the AlgoTest Signals support group on Telegram:
- The copied Debug details
- Timestamp of the issue - when the signal fired (or should have)
- A screenshot of the chart with your indicator at that time
With these three things, support can usually pinpoint the root cause quickly.