Webhooks
Troubleshooting
Common webhook issues and how to fix them, whether your signals come from TradingView, an AI agent, or a custom script.
⚡My signal fired but no trade appeared
Insufficient vault balance. Check that you have enough USDC to cover the position size plus fees.
Slippage exceeded. The oracle price moved more than 2% between signal and execution. The trade reverted. Check the activity log for a slippage rejection.
Bot is stopped or paused. Verify the vault is in a running state on the App page.
RPC congestion. The 5-retry engine handles most transient failures, but sustained congestion can exhaust all retries. Check again after a few minutes.
Invalid or expired token. If you regenerated the vault or changed settings, the webhook token may have changed. Re-copy the URLs from the vault panel.
⚡I'm getting HTTP errors from the webhook URL
401 Unauthorized. The token parameter is missing or incorrect. Copy the full URL from the vault panel again, including the token.
404 Not Found. The vault address in the URL doesn't exist. Double-check the vault parameter.
429 Too Many Requests. You're hitting rate limits. Space out signals to avoid bursting.
500 Server Error. Temporary Amyth API issue. The 5-retry engine handles these automatically for live bots. If persistent, check our Discord for status updates.
⚡I see duplicate trades / double execution
This shouldn't happen. The onchain program has replay protection via nonces. If you see what looks like duplicates, check if your signal source sent two separate requests (e.g., TradingView alert fired twice, or your script has a retry loop that double-fires).
⚡My bot stopped unexpectedly
Liquidation. The position moved against you enough to breach maintenance margin. Jupiter's keeper closed it and your vault stopped the bot. Check the activity log.
Drawdown guard triggered. If you set a max drawdown, the bot stops at that threshold.
Insufficient SOL for gas. Your wallet needs SOL to pay transaction fees. If it ran out, the bot can't submit transactions.
⚡There's a delay between my signal and the trade
Normal latency is 2–10 seconds from HTTP request → onchain confirmation. This includes API processing (~1-2s) and Solana confirmation (~1-3s).
During heavy Solana congestion, latency can increase to 30–60 seconds as retries fire with exponential backoff.
If your signal source has its own latency (e.g., TradingView alert processing), add that to the total.
⚡My AI agent is making too many / wrong trades
This is an agent configuration issue, not an Amyth issue. The vault will faithfully execute every valid signal it receives. It doesn't judge whether the signal is 'good.'
Reduce the agent's authority by tightening your vault's risk rails: lower the max leverage, set a tighter drawdown guard, or reduce the max position size.
Consider having the agent submit to a staging/test endpoint first, or throttle its signal rate.
You can stop the bot instantly from the vault panel to halt all execution while you debug the agent.
Activity log first
Your vault's activity log shows every decision — including rejections, retries, and errors with their status messages. This is the fastest diagnostic tool.
Still stuck?
Message our Telegram bot with /ticket followed by your vault address and issue description. We respond within 1 business day.
Was this page helpful?