Even the best tools can encounter small issues. This guide helps you identify, understand, and resolve the most common problems when using Syra Trading Agent Bot.
⚙️ 1. Bot Doesn’t Respond to Commands
🧠 Possible Causes:
Telegram is temporarily disconnected.
You haven’t pressed Start yet.
n8n webhook URL has changed or stopped.
✅ Solution:
Make sure you started the bot using /start.
Check that the n8n workflow is active and published.
Reconnect your Telegram Trigger Node in n8n and deploy again.
Wait a few seconds and try the command again.
💡 Tip: You can test connectivity using /ping if you’ve added it as a diagnostic command.
💬 2. “Unknown Command” Message
🧠 Cause:
The command you typed doesn’t exist or has a typo.
✅ Solution:
Use /start or /help to see the full list of valid commands.
Ensure commands are written without spaces or extra symbols, e.g.:
✅ /signal bitcoin
❌ /signal-bitcoin or /signal@botname bitcoin
ℹ️ Syra only recognizes commands exactly as defined in your n8n switch node.
📊 3. “No Signal Available” or Empty Response
🧠 Possible Causes:
Market API temporarily unavailable.
The token name is not supported.
n8n function node failed to process indicator data.
✅ Solution:
Check that the token is in your supported list (/list).
Try again later — sometimes data APIs (e.g., Binance) throttle requests.
In n8n, open the workflow logs and inspect the HTTP Request Node output.
🧩 Tip: Add an “Error Branch” in n8n to handle fallback messages automatically.
🪙 4. Wrong Token or Invalid Symbol
🧠 Cause:
The bot couldn’t match your input to a known trading pair.
✅ Solution:
Use /list to confirm the correct token name.
Only use base token names like “bitcoin”, “eth”, or “solana”.
Avoid symbols with dashes or spaces.
✅ Correct: /signal eth
❌ Incorrect: /signal eth/usdt or /signal ethereum coin
🕒 5. Delay in Receiving Signals
🧠 Possible Causes:
Telegram API delay (rare).
n8n function execution taking longer than usual.
Heavy network traffic on the exchange API.
✅ Solution:
Wait up to 10–15 seconds for complex analysis results.
Optimize your n8n nodes (e.g., reduce unnecessary calculations).
Ensure your hosting (e.g., VPS) has stable network performance.
⚡ Pro Tip: Cache recent results for popular tokens to speed up responses.
📈 6. Data or Indicator Errors
🧠 Cause:
Some nodes in n8n returned “undefined” or “NaN” values.
✅ Solution:
Double-check that your Function Node properly converts all numeric data.
Verify all candles contain valid Open, High, Low, Close values.
Add a fallback value or default parameter in your script.
Example:
🧠 This prevents incomplete data from breaking your signal format.
🔐 7. Feedback Not Saved to Database
🧠 Possible Causes:
Database credentials not set in environment variables.
n8n “Insert Row” node misconfigured.
API rate limits exceeded.
✅ Solution:
Test database connection manually in n8n.
Ensure correct table name and schema (feedback, message, timestamp).
Use an Error Trigger Node to capture failed saves.
💬 You can also log user feedback in a simple Google Sheet or Notion database as a fallback.
📘 8. Documentation Link Not Opening
🧠 Cause:
The /docs command URL is missing or incorrect.
✅ Solution:
Check the link in your n8n “Telegram Send Message” node.
Use a full URL, e.g.:
Ensure the GitBook project is published and publicly accessible.
🚫 9. Bot Blocked or Banned
🧠 Cause:
Telegram may block bots that send too many messages or violate content policies.
✅ Solution:
Respect Telegram’s rate limits (no more than 1 msg/sec).
Avoid sending trading “advice” wording — use “analysis” instead.
Make sure your bot doesn’t auto-DM users who didn’t start it manually.
⚠️ Always comply with Telegram’s Bot API Terms of Service.
🧰 10. Workflow Doesn’t Trigger on Command
🧠 Possible Causes:
Telegram Trigger node not configured to “All Messages”.
The webhook URL changed after redeployment.
✅ Solution:
Reopen your Telegram Trigger Node in n8n.
Click Reconnect → select your bot → redeploy.
Check if the workflow is Active.
🧠 Still Having Issues?
If you’ve gone through all steps and still face problems:
Restart your n8n instance.
Run the workflow manually in debug mode.
Check your server logs for API or connection errors.
Contact support or open an issue on your documentation portal.
💡 Pro Tip
Consider adding a /status or /debug command in your n8n workflow to:
Test Telegram connectivity
Check API availability
Show system uptime
It’s a simple way to ensure everything is working before sending live signals.
