Skip to main content

Common Issues and Solutions

This troubleshooting guide addresses the most frequently encountered issues in Nimbus. Use this guide to quickly diagnose and resolve problems with your automated trading strategies.

Strategy Issues

Problems with strategy execution and performance

Connection Problems

Exchange connectivity and API issues

Performance Issues

Slow performance and optimization problems

Account Issues

Account setup and authentication problems

Strategy Not Executing Trades

Verify your strategy is active and properly configuredCommon Causes:
  • Strategy is paused or stopped
  • Insufficient account balance
  • Risk limits exceeded
  • Market conditions don’t meet entry criteria
Solutions:
  1. Navigate to Strategy Dashboard
  2. Check strategy status indicator
  3. Review recent activity logs
  4. Verify account balance exceeds minimum requirements
  5. Check risk management settings
Your account doesn’t have enough funds to execute tradesError Messages:
  • “Insufficient balance for trade execution”
  • “Account balance below minimum threshold”
  • “Not enough collateral for position”
Solutions:
{
  "troubleshooting_steps": [
    "Check current account balance",
    "Review minimum balance requirements",
    "Add funds to your account",
    "Reduce position sizes in strategy settings",
    "Adjust risk parameters to lower requirements"
  ]
}
Strategy stopped due to risk management controlsCommon Triggers:
  • Daily loss limit reached
  • Maximum drawdown exceeded
  • Position size limit violated
  • Correlation limits breached
Resolution Steps:
  1. Review risk management dashboard
  2. Check which limit was exceeded
  3. Adjust risk parameters if appropriate
  4. Wait for daily limits to reset
  5. Consider strategy modifications

Poor Strategy Performance

Trades executing at worse prices than expected Symptoms: - Large difference between expected and actual fill prices - Reduced profitability compared to backtests - Frequent partial fills Causes and Solutions: - Low Liquidity Assets: Switch to more liquid trading pairs - Large Position Sizes: Reduce position sizes relative to market volume - Market Volatility: Adjust order types and timing - Poor Timing: Avoid trading during low volume periods
Strategies getting stopped out too frequently Analysis Steps: mermaid graph TD A[Frequent Stops] --> B[Check Volatility] A --> C[Review Stop Distance] A --> D[Analyze Entry Quality] B --> B1[High Volatility Period?] B1 --> B2[Widen Stops Temporarily] C --> C1[Stops Too Tight?] C1 --> C2[Use ATR-Based Stops] D --> D1[Poor Entry Timing?] D1 --> D2[Add Confirmation Filters] Solutions: - Use volatility-adjusted stop losses - Implement multiple confirmation signals - Consider market regime in stop placement - Review and optimize entry criteria
Strategy winning fewer trades than expected Diagnostic Questions: - Is this a new market regime? - Have market conditions changed? - Are entry signals still valid? - Is the strategy over-optimized? Improvement Actions: 1. Market Analysis: Check if current conditions match strategy assumptions 2. Signal Quality: Review and potentially add filters 3. Parameter Adjustment: Consider modest parameter changes 4. Portfolio Approach: Diversify across multiple strategies

Strategy Configuration Errors

Strategy fails to start due to configuration issuesCommon Errors:
{
  "parameter_errors": {
    "position_size": "Cannot exceed 100% of account",
    "stop_loss": "Must be positive value less than 50%",
    "take_profit": "Must be greater than stop loss",
    "timeframe": "Unsupported timeframe selected",
    "indicators": "Period cannot be greater than available data"
  }
}
Validation Checklist:
Contradictory entry/exit conditions preventing executionExamples:
  • Entry requires RSI < 30 AND RSI > 70 (impossible)
  • Long and short signals triggered simultaneously
  • Stop loss set above entry price for long positions
Resolution:
  1. Review all strategy conditions systematically
  2. Test logic with sample data
  3. Simplify complex rule sets
  4. Use strategy validation tools

Exchange and API Issues

Connection Problems

Cannot connect to exchange APIsError Messages:
  • “Connection timeout”
  • “API key authentication failed”
  • “Exchange unreachable”
  • “SSL certificate error”
Troubleshooting Steps:
  1. Check Exchange Status: Verify exchange is operational
  2. API Key Validation: Ensure keys are correct and active
  3. Network Connectivity: Test internet connection
  4. Firewall Settings: Check for blocking rules
  5. Rate Limiting: Verify not exceeding API limits
Requests being throttled by exchangeSymptoms:
  • Delayed order execution
  • “Rate limit exceeded” errors
  • Partial data updates
  • Increased latency
Solutions:
{
  "rate_limit_fixes": {
    "reduce_frequency": "Lower update frequencies",
    "batch_requests": "Combine multiple requests",
    "upgrade_account": "Higher tier accounts get more requests",
    "distribute_load": "Use multiple API keys if allowed",
    "optimize_calls": "Cache data when possible"
  }
}
API key or authentication issuesCommon Causes:
  • Expired API keys
  • Incorrect permissions
  • IP address restrictions
  • Wrong passphrase or secret
Resolution Steps:
  1. Regenerate API Keys: Create new keys with proper permissions
  2. Check Permissions: Ensure trading permissions enabled
  3. IP Whitelist: Add current IP to allowed list
  4. Test Connection: Use exchange’s API testing tools

Order Execution Issues

Orders placed but not executingPossible Reasons:
  • Price moved away from limit order
  • Insufficient liquidity at price level
  • Order size too large for market
  • Exchange technical issues
Diagnostic Steps:
Orders only partially executedUnderstanding Partial Fills:
  • Large orders may fill in multiple parts
  • Normal in illiquid markets
  • Can affect strategy performance
Management Strategies:
  • Accept Partials: Allow partial fills for large orders
  • Size Reduction: Use smaller order sizes
  • Time Limits: Set maximum time for order completion
  • Iceberg Orders: Break large orders into smaller pieces
Significant difference between expected and actual fill pricesSlippage Causes:
  • Market volatility
  • Low liquidity
  • Large order sizes
  • Network latency
Mitigation Techniques:
  1. Limit Orders: Use limit orders instead of market orders
  2. Size Management: Reduce order sizes in volatile markets
  3. Timing: Avoid trading during low liquidity periods
  4. Slippage Tolerance: Set acceptable slippage limits

Performance and Technical Issues

Slow Performance

Web interface taking too long to loadQuick Fixes:
  • Clear browser cache and cookies
  • Disable browser extensions
  • Try incognito/private browsing mode
  • Switch to different browser
  • Check internet connection speed
Advanced Solutions:
  • Reduce chart timeframe or indicators
  • Limit number of strategies displayed
  • Close unnecessary browser tabs
  • Restart browser or device
Trades executing later than expectedLatency Sources:
{
  "latency_breakdown": {
    "signal_generation": "1-5 seconds",
    "strategy_processing": "0.1-1 seconds", 
    "order_routing": "0.1-0.5 seconds",
    "exchange_processing": "0.1-2 seconds",
    "network_latency": "0.01-0.1 seconds"
  }
}
Optimization Tips:
  • Use faster execution modes
  • Simplify strategy logic
  • Reduce number of indicators
  • Choose closer server locations
System resources being overutilizedResource Optimization:

Data Issues

Gaps or missing data in charts and analysis Common Causes: - Exchange downtime - Network connectivity issues - Data provider problems - Maintenance periods Solutions: 1. Data Backfill: Request historical data refresh 2. Multiple Sources: Use backup data providers 3. Cache Management: Clear data cache and reload 4. Time Adjustment: Check timezone settings
Technical indicators showing unexpected values Verification Steps:

Error Messages and Codes

Common Error Codes

| Error Code | Description | Solution | |------------|-------------|----------| | 1001 | Invalid API Key | Regenerate API key with proper permissions | | 1002 | Insufficient Balance | Add funds or reduce position size | | 1003 | Rate Limit Exceeded | Reduce request frequency | | 2001 | Strategy Validation Failed | Check strategy parameters | | 2002 | Risk Limit Violated | Adjust risk settings | | 3001 | Exchange Connection Lost | Check network and exchange status | | 3002 | Order Rejected | Verify order parameters | | 4001 | Data Feed Interrupted | Check data provider status | | 5001 | System Maintenance | Wait for maintenance completion |
Different exchanges may return unique error messages Hyperliquid Common Errors: - “Insufficient margin”: Need more collateral - “Invalid size”: Order size outside allowed range - “Rate limited”: Too many requests - “Market closed”: Trading not available General Exchange Errors: - “Symbol not found”: Invalid trading pair - “Order not found”: Order already filled or cancelled - “Precision error”: Incorrect decimal places - “Minimum size”: Order below minimum amount

Diagnostic Tools

Built-in Diagnostics

Use Nimbus’s built-in diagnostic tools Health Check Items:Accessing Diagnostics: 1. Navigate to Strategy Dashboard 2. Click “Health Check” button 3. Review all diagnostic results 4. Follow recommended actions
Test exchange connectivity and API functionality Test Components: - Network latency measurement - API authentication verification - Market data feed quality - Order routing functionality - Error handling capabilities Running Tests: bash # Example diagnostic commands curl -X GET "https://api.hyperliquid.xyz/info" # Test basic connectivity ping api.hyperliquid.xyz # Check network latency
Monitor system and strategy performance metrics Key Metrics: - Order execution latency - Strategy signal generation time - Data feed reliability
  • System resource usage - Network connectivity quality Monitoring Dashboard: - Real-time performance graphs - Historical trend analysis - Alert configuration - Comparative benchmarks

Getting Additional Help

Support Resources

Comprehensive resources for learning and troubleshooting Available Resources: - User Manual: Complete feature documentation - Video Tutorials: Step-by-step visual guides - FAQ Database: Common questions and answers - Best Practices: Recommended approaches - API Documentation: Technical integration guides
Connect with other users and experts Community Channels: - Discord Server: Real-time chat and support - Telegram Groups: Strategy discussions - Reddit Community: Tips and experiences - YouTube Channel: Educational content - Blog and Updates: Latest features and news
Contact Nimbus support team Support Channels: - Email Support: support@nimbus.trade - Live Chat: Available during business hours - Ticket System: Track support requests - Priority Support: Available for premium users Before Contacting Support:

Preparing for Support

Collect relevant information before contacting support System Information: - Operating system and version - Browser type and version - Internet connection speed - Time zone and location Account Information:
  • Account email address - Subscription tier - Connected exchanges - Affected strategies Issue Details: - Exact error messages - Steps to reproduce - When issue first occurred - Screenshots or screen recordings
How to communicate issues clearly for faster resolution Best Practices:
  1. Be Specific: Provide exact error messages 2. Include Context: Describe what you were trying to do 3. Provide Examples: Include specific trades or strategies 4. Be Patient: Allow time for investigation 5. Follow Up: Provide additional information if requested Sample Support Request: ``` Subject: Strategy not executing trades - Error 2001 Hello, I’m experiencing an issue with my DCA strategy on BTC/USDT. The strategy shows as “Active” but hasn’t executed any trades for the past 3 hours. Error message: “Strategy Validation Failed - Error Code 2001” Strategy details: - Name: BTC DCA Conservative - Exchange: Hyperliquid
  • Position size: 1% of account - Account balance: $10,000 Screenshots attached showing the error and strategy settings. Please help resolve this issue. Best regards, [Your name] ```

Preventive Measures

Best Practices for Avoiding Issues

Next Steps

I