Common Errors

Quick reference for resolving the most frequently encountered errors on TradeStaq.

Error Categories

Connection Errors

"Exchange Connection Failed"

Error Message:

Failed to connect to exchange. Please check your API credentials.

Causes:

Solutions:

1. Verify API key is correct (no extra spaces)
2. Check API secret (hidden characters?)
3. Verify key hasn't expired on exchange
4. Add TradeStaq IP to whitelist (if enabled)
5. Try creating new API keys

"API Key Invalid"

Error Message:

The provided API key is invalid or has been revoked.

Solutions:

1. Log into your exchange
2. Go to API Management
3. Verify the key exists and is active
4. If deleted, create new keys
5. Update credentials in TradeStaq

"Insufficient Permissions"

Error Message:

API key does not have required permissions for this operation.

Required Permissions:

Solution: Update API key permissions on your exchange.

"IP Whitelist Error"

Error Message:

Request rejected: IP address not whitelisted.

Solutions:

1. Log into your exchange
2. Go to API key settings
3. Either:
   • Add TradeStaq's IP addresses
   • Disable IP restriction (less secure)
4. Wait 5 minutes for changes to propagate

Trading Errors

"Insufficient Balance"

Error Message:

Insufficient balance to execute trade. Required: $X, Available: $Y

Solutions:

"Order Rejected"

Error Message:

Order rejected by exchange: [reason]

Common Reasons:

"Position Not Found"

Error Message:

Cannot close position: No open position found for [symbol].

Causes:

• Position already closed
• Wrong symbol specified
• Position on different exchange
• Manual close on exchange

Solutions:

1. Refresh positions page
2. Check exchange directly
3. Verify correct bot/exchange

"Leverage Not Supported"

Error Message:

Requested leverage [X]x exceeds maximum allowed [Y]x.

Solutions:

1. Reduce leverage in bot settings
2. Check exchange's leverage limits for the pair
3. Some pairs have lower max leverage

Bot Errors

"Bot Limit Reached"

Error Message:

Cannot create bot: Bot limit reached for your subscription tier.

Tier Limits:

Solutions:

1. Delete unused bots
2. Upgrade subscription tier
3. Consolidate strategies

"Webhook Not Receiving"

Symptoms:

• Webhook health is yellow/red
• Signals not executing
• No recent activity

Diagnostic Steps:

Solutions:

1. Copy fresh webhook URL
2. Test with curl/Postman
3. Verify JSON payload format
4. Check bot is active

"Invalid Signal Format"

Error Message:

Invalid webhook payload: [details]

Common Format Issues:

"Strategy Execution Error"

Error Message:

Strategy execution failed: [error details]

Common Causes:

• Indicator calculation failed
• Invalid state access
• Timeout exceeded

Solutions:

1. Check strategy logs in bot detail page
2. Verify all parameters are set
3. Report if built-in strategy

Account Errors

"Session Expired"

Error Message:

Your session has expired. Please log in again.

Causes:

• Inactive for extended period
• Password changed
• Manual logout elsewhere

Solution: Log in again.

"Subscription Required"

Error Message:

This feature requires [Tier] subscription or higher.

Feature Requirements:

Solution: Upgrade subscription to access feature.

"Resource Paused"

Error Message:

This [bot/exchange] has been paused due to subscription downgrade.

Context: After downgrading, excess resources are soft-paused.

Solutions:

1. Delete excess resources
2. Upgrade back to previous tier
3. Choose which resources to keep

Webhook Errors

"Rate Limit Exceeded"

Error Message:

Rate limit exceeded. Please slow down requests.

Limits:

• 60 requests per minute per webhook
• 10 requests per second burst

Solutions:

1. Add delays between signals
2. Review strategy to reduce signal frequency
3. Upgrade tier for higher limits

"Webhook Timeout"

Error Message:

Webhook request timed out.

Causes:

• Network issues
• Server overload
• Large payload

Solutions:

1. Retry the request
2. Reduce payload size
3. Check network connection
4. Try again later

Quick Fixes Checklist

Before Contacting Support

• Refresh the page
• Clear browser cache
• Try incognito/private mode
• Check exchange status page
• Verify API credentials
• Review bot logs
• Check subscription status
• Test webhook manually

Information to Gather

When contacting support, include:

Next Steps

• Exchange Issues - Exchange-specific problems
• Bot Issues - Bot troubleshooting
• FAQ - Frequently asked questions