Trading Bot Troubleshooting Guide — Common Errors and Fixes on BitcoinEra

Every Problem. Diagnosed and Resolved.

Something isn’t working. Your bot is showing an error. A trade didn’t execute when it should have. The connection keeps dropping. The performance isn’t matching what you expected.

This guide is your complete diagnostic resource — organized by problem type, with step-by-step resolution paths for every common issue encountered on BitcoinEra. We’ve structured it so you can quickly find the specific problem you’re experiencing and follow a clear path to resolution — without wading through information that isn’t relevant to your situation.

Use the section headers to navigate directly to your issue type. Every problem section follows the same format: what the error looks like, what causes it, and exactly how to fix it — in order from most common to least common cause.

---

How to Use This Guide

Step 1: Identify your problem category from the section list below. Step 2: Navigate to that section. Step 3: Match your specific error message or symptom to the relevant entry. Step 4: Follow the resolution steps in order — starting with Step 1. Don’t skip ahead. Step 5: If the problem persists after all steps — contact support with the information listed at the end of each section.

---

Problem Categories

1. API Connection Errors
2. Bot Won’t Start or Activate
3. Trade Execution Problems
4. Performance and Configuration Issues
5. Dashboard and Display Problems
6. Account and Login Issues
7. Notification Problems
8. Exchange-Specific Issues
9. Mobile App Issues
10. When to Contact Support

---

Category 1 — API Connection Errors

API connection errors are the most common technical issue on the platform. They occur when the connection between BitcoinEra and your exchange breaks down for any reason.

Error: “Invalid API Key”

What it looks like: Red connection indicator. Error message: “Invalid API Key”, “API key does not exist”, or “Authentication failed.”

What causes it:

Cause A — Credentials entered incorrectly (most common) A single wrong character — a missing letter, an extra space, a capital where lowercase is expected — causes this error. API keys are case-sensitive and exact.

Resolution:

1. Go to your exchange API Management page
2. Find the API key associated with this bot
3. Copy the API Key exactly — using copy-paste, not manual typing
4. Go to BitcoinEra → Connected Exchanges → Edit this connection
5. Delete the existing API Key value completely
6. Paste the fresh copy
7. Repeat for Secret Key (and Passphrase if OKX)
8. Save and test connection

---

Cause B — API key was deleted from the exchange If someone (including yourself) deleted the API key from the exchange’s API Management page — it no longer exists and cannot authenticate.

Resolution:

1. Log in to your exchange → API Management
2. Verify whether the key still exists
3. If deleted — create a new API key following the relevant guide:
   • [How to Create an API Key on Binance →]
   • [How to Create an API Key on Bybit →]
   • [How to Create an API Key on OKX →]
4. Connect the new key in BitcoinEra

---

Cause C — API key expired Some exchanges allow API keys to be configured with an expiry date. If your key has passed its expiry — it will show as invalid.

Resolution:

1. Log in to your exchange → API Management
2. Check the expiry date on your key
3. If expired — create a new key without an expiry date
4. Connect the new key in BitcoinEra

---

Cause D — Wrong exchange selected A Binance API key entered in a Bybit connection will fail. API keys are exchange-specific and not interchangeable.

Resolution:

1. Verify which exchange the API key was created on
2. In BitcoinEra — verify the exchange dropdown matches
3. If mismatched — select the correct exchange and re-enter credentials

---

Information to include if contacting support:

• Exchange name
• Error message text (exact)
• When the error first appeared
• Whether the connection was previously working

---

Error: “Insufficient Permissions”

What it looks like: Connection establishes but bot fails to place trades. Error message: “Insufficient permissions”, “Permission denied”, or “This API key does not have trading permission.”

What causes it:

Cause A — Spot Trading permission not enabled (most common)

Resolution:

1. Log in to your exchange → API Management
2. Find your API key → Edit
3. Verify “Spot Trading” (or equivalent) is checked
4. Save the updated permissions
5. Test connection in BitcoinEra — should resolve within 1–2 minutes

---

Cause B — Wrong account type permissions On Bybit — if you have a Unified Trading Account but your API key was created without Unified Account permissions.

Resolution:

1. Log in to Bybit → API Management
2. Edit your key
3. Enable “Unified Account” permission alongside Spot Trading
4. Save and test

---

Cause C — Regional restrictions on specific trading features Some exchanges restrict certain trading features in specific jurisdictions. If you’re in a restricted region — some permissions may not be grantable.

Resolution:

1. Check your exchange’s regional restrictions documentation
2. Verify your account’s KYC level is sufficient for API trading
3. Contact your exchange support for region-specific guidance

---

Error: “IP Address Not Authorized”

What it looks like: Error message: “IP restriction violation”, “Access denied from this IP”, or “Request IP not in whitelist.”

What causes it:

Cause A — IP restriction enabled but BitcoinEra server IP not whitelisted

Resolution:

1. Contact BitcoinEra support to obtain the current server IP address
2. Log in to your exchange → API Management → Edit your key
3. Add the BitcoinEra server IP to the approved list
4. Save and test connection

---

Cause B — Your home/server IP changed since setting up the restriction If you restricted the key to your own IP address and your IP has changed (dynamic IP).

Resolution:

1. Log in to your exchange → API Management
2. Either update the IP address to your current one
3. Or remove IP restriction entirely if you don’t have a fixed IP

---

Cause C — Multiple IP addresses needed (if running other tools alongside BitcoinEra)

Resolution:

1. Log in to your exchange → API Management → Edit your key
2. Add all required IP addresses (most exchanges allow multiple)
3. Include both your own IP and the BitcoinEra server IP

---

Error: “Connection Timed Out” or “Request Failed”

What it looks like: Intermittent connection errors. Dashboard shows connection as unstable or repeatedly connecting/disconnecting.

What causes it:

Cause A — Exchange experiencing degraded performance or partial outage

Resolution:

1. Check the exchange’s official status page:
   • Binance: status.binance.com
   • Bybit: status.bybit.com
   • OKX: okxcomstatus.com
2. If exchange is showing degraded status — wait for resolution. Bot will reconnect automatically when exchange performance normalizes.
3. If exchange shows no issues — proceed to Cause B.

---

Cause B — Temporary network issue between BitcoinEra servers and exchange

Resolution:

1. Wait 15–30 minutes — transient network issues typically resolve automatically
2. Check BitcoinEra’s own status page for any announced issues
3. If problem persists beyond 1 hour — contact support

---

Cause C — API rate limit exceeded High-frequency bots may occasionally exceed exchange API rate limits during periods of intense market activity.

Resolution:

1. Check your bot’s configuration — is position sizing creating more API calls than expected?
2. Review the specific bot’s documentation for rate limit guidance
3. If using multiple bots on the same exchange — they share the API rate limit. Multiple active bots may collectively exceed the limit.
4. Contact support with your bot list and exchange for rate limit analysis

---

Category 2 — Bot Won’t Start or Activate

Problem: Bot Shows “Connecting” Status Indefinitely

What it looks like: Bot status shows “Connecting” with animated indicator for more than 5 minutes without resolving to Active or Error.

Resolution steps:

1. Refresh your dashboard (F5 or browser refresh)
2. If still showing Connecting after refresh — go to Connected Exchanges and verify the connection status
3. If connection shows Error — follow Category 1 guidance for the specific error
4. If connection shows Active but bot still Connecting — disconnect and reconnect the bot
5. If problem persists — contact support with your bot name and exchange

---

Problem: Bot Activates But Immediately Stops

What it looks like: Bot changes to Active briefly then immediately changes to Stopped or Error.

Cause A — Insufficient balance for configured minimum capital

Resolution:

1. Check your exchange balance — is it above the bot’s minimum capital requirement?
2. Check your allocated capital setting — is it within your available balance?
3. Reduce allocated capital to within your available balance or deposit more funds to your exchange

---

Cause B — Configuration parameter error An invalid configuration value is preventing the bot from initializing.

Resolution:

1. Go to the bot’s Settings
2. Review each parameter against the valid ranges in the bot’s documentation
3. Reset to default values and reactivate
4. If it activates successfully — adjust settings one at a time to identify the problematic parameter

---

Cause C — Trading pair not available on your exchange account The configured trading pair may not be available in your region or account type.

Resolution:

1. Log in to your exchange directly
2. Verify the BTC/USDT (or configured pair) is accessible in your account
3. Some regions have pair restrictions — contact your exchange if the pair is not available

---

Category 3 — Trade Execution Problems

Problem: Bot Is Not Making Any Trades

What it looks like: Bot status shows Active. Connection is green. Zero trades in history after 24+ hours.

Cause A — Normal strategy behavior (most common) Many strategies don’t trade continuously — they wait for specific conditions. This is not a malfunction.

Diagnosis:

1. Check the bot’s strategy documentation — what is the expected trading frequency?
2. Check current market conditions — are they favorable for this strategy?
3. A trend following bot in a sideways market may legitimately make no trades for days or weeks
4. Wait at least 48–72 hours before investigating further for low-frequency strategies

---

Cause B — Allocated capital below minimum position size The bot has capital allocated but it’s insufficient for even one minimum-sized trade.

Resolution:

1. Check the bot’s minimum capital requirement
2. Verify your allocated capital exceeds this minimum
3. Check the minimum trade size for BTC/USDT on your exchange (typically $10–$20 minimum)
4. Ensure allocated capital ÷ maximum positions > exchange minimum trade size

---

Cause C — All capital already deployed in open positions The bot has reached its maximum open positions limit and all capital is committed.

Resolution:

1. Check open positions in your dashboard
2. If positions are open — the bot is working. It’s waiting for them to close before opening new ones.
3. If this is happening more than expected — review your maximum open positions setting

---

Cause D — Market is outside the bot’s operating parameters Grid bots don’t trade when price is outside grid boundaries. RSI bots don’t trade when RSI is in neutral territory. Range-bound strategies don’t trade when the market is trending strongly.

Resolution:

1. Check the bot’s current operational status in its detail view
2. Compare current market conditions to the strategy’s documented operating conditions
3. If the market has moved outside the strategy’s intended range — this is a strategy mismatch issue, not a technical problem

---

Problem: Trades Are Executing at Wrong Prices

What it looks like: Trade history shows entry or exit prices significantly different from the price you saw when the trade should have executed.

Cause A — Slippage on market orders during volatile conditions Market orders fill at the best available price at execution time — which may differ from the quoted price during fast market moves.

Resolution: This is normal market behavior — not a malfunction. To reduce slippage:

1. Review whether your bot uses market or limit orders
2. If market orders — consider a bot that uses limit orders for better price control
3. Avoid allocations large enough that your orders significantly impact the order book

---

Cause B — Price data latency The price shown in your dashboard may have a brief delay compared to the price at which the order was actually executed.

Resolution: Compare the execution price in your dashboard against your exchange’s own trade history (using the Exchange Order ID). If they match — the price was correct at execution time, even if it looks different from what the dashboard showed when you checked.

---

Problem: Stop Loss or Take Profit Not Triggering

What it looks like: Price has clearly passed the configured stop loss or take profit level but the position is still open.

Cause A — Limit order not filled (no liquidity at exact price) If the bot uses limit orders for stop loss/take profit — the order sits at the specified price waiting for the other side. In fast-moving markets, the price can pass through the level without filling.

Resolution:

1. Check your exchange’s order book for the open stop/take profit order
2. If the order is there but unfilled — the price moved through faster than it could fill
3. This is exchange behavior — not a BitcoinEra issue. Consider whether your bot’s exit order type (limit vs market) is appropriate for your strategy

---

Cause B — Exchange API delay during high-traffic periods During extreme market volatility — exchanges experience high load. Stop loss orders placed via API may have a brief delay.

Resolution: This is a market infrastructure issue. Reduce exposure during known high-volatility events. Consider native exchange stop orders (placed directly on the exchange) for your most critical risk parameters if API delay is a concern.

---

Cause C — Configuration error — stop loss set on wrong side A long position with a stop loss accidentally set above the entry price would never trigger (it would trigger immediately when entered). Similarly, a take profit below entry would do the same.

Resolution:

1. Check your bot’s open positions
2. Verify stop loss is below entry price for long positions
3. Verify take profit is above entry price for long positions
4. If misconfigured — contact support for guidance on safely correcting the open position

---

Category 4 — Performance and Configuration Issues

Problem: Performance Significantly Below Historical Average

What it looks like: Bot has been running for 4+ weeks and returns are substantially below the historical performance shown in the catalog.

Diagnosis framework:

Step 1 — Check market conditions Are current market conditions aligned with this strategy’s strengths? A grid bot during a strong trend will underperform. A trend following bot during choppy sideways will underperform. This is expected behavior — not a malfunction.

Step 2 — Compare win rate Is your live win rate consistent with the bot’s historical win rate? A significant downward deviation (more than 10 percentage points below historical) over 4+ weeks suggests strategy misalignment or a configuration issue.

Step 3 — Check exit reason distribution Are stop losses triggering more frequently than expected? This may indicate your stop loss is set too tight for current volatility — or that the strategy genuinely isn’t suited to current conditions.

Step 4 — Verify configuration hasn’t changed Review your current settings against your original configuration. Has anything changed — accidentally or through a platform update?

Step 5 — Contact the bot author If steps 1–4 don’t explain the underperformance — reach out to the bot author directly through their profile. They know their strategy best and may be aware of a specific issue.

---

Problem: Drawdown Exceeding Expectations

What it looks like: Bot drawdown is deeper than the historical maximum drawdown shown in the catalog.

Assessment: First — verify the comparison is fair. The catalog shows maximum drawdown during the tracked period. If market conditions since you connected the bot are worse than anything during the track record period — deeper drawdown may be statistically expected, not anomalous.

Resolution steps:

1. Compare current market conditions to historical — is this a historically unusual market event?
2. Review whether the bot author has communicated anything about current conditions
3. Verify your drawdown limit is correctly configured — it should activate before losses become catastrophic
4. If drawdown is within your configured limit and within historical parameters — allow the strategy time to recover
5. If drawdown has exceeded historical maximum without apparent extraordinary cause — contact support

---

Problem: Position Sizes Inconsistent With Settings

What it looks like: Trades are opening at sizes larger or smaller than your configuration settings suggest they should be.

Cause A — Percentage-based position sizing calculated on changing capital If position size is set as a percentage of current capital — and capital has grown or shrunk from the initial allocation — trade sizes change accordingly.

Resolution: This is correct behavior. Percentage-based sizing means trade sizes scale with capital. If you want fixed dollar sizes — check whether your bot supports fixed value position sizing.

---

Cause B — DCA safety order accumulation In DCA bots — safety orders are typically larger than the base order. If you’re seeing large orders, they may be safety orders operating as designed.

Resolution: Review your DCA configuration — base order size, safety order size, and volume scale. Calculate what each order level should be and compare to actual trade sizes in history.

---

Cause C — Configuration was changed since activation If someone (including yourself on another device) changed the position sizing settings after activation — trades will reflect the new settings from that point forward.

Resolution: Check your configuration settings and your change history in the bot’s settings panel.

---

Category 5 — Dashboard and Display Problems

Problem: Balance Shows Incorrectly

What it looks like: Balance shown in BitcoinEra dashboard doesn’t match your actual exchange balance.

Cause A — Sync delay (most common) BitcoinEra reads exchange balance at defined intervals — not in real-time continuously. There is typically a 1–5 minute lag between a trade closing and the dashboard reflecting the updated balance.

Resolution: Wait 5 minutes and refresh. If the balance still doesn’t match — proceed to Cause B.

---

Cause B — Unrealized P&L on open positions If the bot has open positions, the current value includes unrealized gains or losses at the current market price. Your “available balance” on the exchange doesn’t include funds committed to open positions.

Resolution: Compare total position value (open positions at current prices) + available balance against the dashboard total. They should reconcile.

---

Cause C — Manual trades placed directly on exchange If you’ve made manual trades on your exchange outside the bot — those affect your exchange balance but may not be fully reflected in BitcoinEra’s allocation tracking.

Resolution: BitcoinEra tracks the allocation it manages. Manual trades outside the bot’s allocation are your exchange balance but separate from the bot’s tracked capital. Check both sources separately.

---

Problem: Trade History Not Loading or Incomplete

What it looks like: Trade history shows fewer trades than expected or won’t load.

Resolution steps:

1. Check your date range filter — it may be set to a shorter period than your bot’s history
2. Check your bot filter — you may be filtered to only one bot when you want all
3. Try clearing browser cache and cookies then reloading
4. Try a different browser
5. If trade history is genuinely missing — contact support with the approximate dates of missing trades and your bot name

---

Problem: Performance Charts Not Displaying

What it looks like: Charts show as blank, loading indefinitely, or displaying errors.

Resolution steps:

1. Hard refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac)
2. Disable browser extensions that might block scripts (particularly ad blockers)
3. Try a different browser
4. Check if you have JavaScript enabled — charts require JavaScript
5. Try the BitcoinEra mobile app if browser issues persist

---

Category 6 — Account and Login Issues

Problem: Cannot Log In

What it looks like: Login fails despite entering what you believe are correct credentials.

Resolution steps:

1. Verify email address: Ensure you’re using the exact email address registered on your account — no typos.
2. Reset password: Click “Forgot Password” on the login page → Enter your email → Check inbox for reset link → Follow link → Set new password → Log in.
3. Check spam folder: If you don’t receive the reset email within 5 minutes — check spam/junk. Add BitcoinEra’s email to your allowlist.
4. Verify account status: If you’ve received any account suspension notifications — your login may be blocked. Contact support.
5. 2FA issues: If 2FA code is not working — ensure your phone’s time is correct (TOTP codes depend on accurate system time). If your authenticator app is out of sync — use a backup code to log in then reconfigure 2FA.
6. Lost 2FA access: If you’ve lost your 2FA device and don’t have backup codes — contact support with your registered email, account creation date, and any verification information you can provide. Identity verification will be required.

---

Problem: Account Shows Unexpected Activity

What it looks like: Trades you didn’t authorize. Settings changed you didn’t make. Login history shows unrecognized sessions.

Immediate actions (do these first):

1. Change your password immediately — Account Settings → Security → Change Password
2. Revoke all active sessions — Account Settings → Security → Active Sessions → Revoke All
3. Review and remove API keys — Account Settings → Connected Exchanges → Review all connections — remove any you don’t recognize
4. Enable or regenerate 2FA — If 2FA was not enabled, enable it now. If it was enabled, disable and re-enable to regenerate codes.
5. Contact support immediately — Provide a summary of what unauthorized activity you’ve identified. Include timestamps.

After securing your account: Review your exchange accounts directly — log in to each exchange and review recent trade history, API keys, and account activity. If any unauthorized trades occurred — contact your exchange support as well.

---

Category 7 — Notification Problems

Problem: Not Receiving Email Notifications

Resolution steps:

1. Check spam/junk folder — add BitcoinEra sender to allowlist
2. Verify email address in Account Settings → Profile is correct
3. Check notification settings — verify the specific notification type is enabled
4. Send a test notification — Notifications → Email → Send Test
5. Check if your email provider is blocking automated emails — try adding BitcoinEra’s IP to your email whitelist
6. If using a corporate email — IT filtering may be blocking. Try a personal email address.

---

Problem: Not Receiving Push Notifications

Resolution steps:

1. Verify notification permissions: Device Settings → BitcoinEra → Notifications → Allow
2. Check Do Not Disturb / Focus mode is not active
3. Verify the BitcoinEra app is up to date
4. Toggle push notifications off and on in BitcoinEra settings
5. Log out of mobile app and log back in
6. Uninstall and reinstall the mobile app (your account data is preserved)

---

Problem: Telegram Notifications Not Arriving

Resolution steps:

1. Open Telegram and search for the BitcoinEra bot
2. Verify the bot shows as active (not blocked)
3. Send a message to the bot — it should respond confirming connection
4. In BitcoinEra settings — disconnect and reconnect the Telegram integration
5. Re-verify with a test notification

---

Category 8 — Exchange-Specific Issues

Binance-Specific Issues

“This function is not available for sub-accounts”

Your API key may be for a sub-account rather than a main account. Sub-account API capabilities are restricted.

Resolution: Create the API key on your main Binance account rather than a sub-account, or enable sub-account API permissions if available in your account settings.

“Timestamp for this request is outside of the recvWindow”

Your system clock is significantly out of sync with Binance’s servers.

Resolution: Sync your device’s clock. On Windows: Settings → Time & Language → Sync Now. On Mac: System Preferences → Date & Time → Set Automatically.

“Account has insufficient balance for requested action”

Available balance is less than the trade size the bot is attempting.

Resolution: Either reduce allocated capital, reduce position sizes, or deposit more USDT to your Binance account.

---

Bybit-Specific Issues

“Unified Account not supported by this key”

API key was created for Standard Account but your account is a Unified Trading Account.

Resolution: Delete the existing API key. Create a new key and specifically enable Unified Account permissions when setting up.

“Risk limit exceeded”

Bybit has risk limit controls that can restrict order placement in certain conditions.

Resolution: Check your Bybit account’s risk limit settings. This may require contacting Bybit support for your specific situation.

---

OKX-Specific Issues

“Wrong Passphrase”

The Passphrase entered in BitcoinEra doesn’t match what was set when creating the API key.

Resolution:

1. Retrieve your Passphrase from your password manager
2. In BitcoinEra → Connected Exchanges → Edit the OKX connection
3. Re-enter the Passphrase exactly as originally created (case-sensitive)
4. If you’ve genuinely forgotten the Passphrase — delete the OKX API key and create a new one

“Account mode mismatch”

OKX has multiple account modes (Simple, Single-Currency Margin, Multi-Currency Margin, Portfolio Margin). The bot may require a specific mode.

Resolution: Check the bot’s documentation for OKX account mode requirements. Verify your OKX account is in the required mode.

---

Category 9 — Mobile App Issues

Problem: App Shows Different Data Than Web Dashboard

What it looks like: Trade history or performance figures differ between the mobile app and the web dashboard.

Resolution:

1. Pull to refresh on the mobile app to force a data sync
2. Log out and log back in to the mobile app
3. Check if you have offline/cached data mode enabled in app settings
4. If discrepancy persists — the web dashboard is the authoritative source. Contact support with screenshots of both.

---

Problem: App Crashes or Won’t Load

Resolution steps:

1. Close the app completely and reopen
2. Check for updates in your app store
3. Restart your device
4. Clear app cache: Device Settings → Apps → BitcoinEra → Clear Cache
5. Uninstall and reinstall (your account data is preserved — it’s stored server-side)

---

Category 10 — When to Contact Support

Most issues covered in this guide can be resolved without contacting support by following the steps provided. But some situations genuinely require the support team’s involvement.

Contact Support Immediately For:

• Suspected unauthorized access to your account
• Funds appear to be missing from your exchange that you can’t account for
• A bot placed trades you genuinely cannot explain
• API connection errors that persist after creating a new API key
• Any situation where you believe financial harm may be occurring or imminent

---

Contact Support Within 24 Hours For:

• Technical errors that persist after following all troubleshooting steps
• Performance data discrepancies between BitcoinEra and your exchange
• Account access issues that password reset hasn’t resolved
• Export or reporting functionality not working correctly
• Billing or fee calculation questions

---

What to Include When Contacting Support

The more information you provide upfront — the faster the support team can help. Always include:

Account information:

• Registered email address
• Account ID (found in Account Settings → Profile)

Problem description:

• Exact error message text (screenshot preferred)
• When the problem first occurred
• What you were doing when it happened
• Whether it was previously working

Bot and exchange details:

• Bot name and ID
• Exchange (Binance/Bybit/OKX)
• API key label (never the actual key)

Steps already taken:

• What troubleshooting steps you’ve already tried
• Results of each step

Supporting materials:

• Screenshots of error messages
• Screenshots of relevant dashboard sections
• Trade IDs for any specific problematic trades

---

Support Contact Channels

In-platform support: Dashboard → Help → Contact Support → Submit Ticket

Email: [email protected]

Response times:

• Critical issues (potential fund risk, account security): Same day
• Technical errors affecting bot operation: 1–2 business days
• General questions and non-urgent issues: 2–3 business days

Community support: For non-urgent questions — the BitcoinEra Telegram community often has faster informal answers from experienced users. Join via the link in your dashboard footer.

---

Quick Reference — Error Codes

Error Code	Meaning	First Action
ERR_API_001	Invalid API credentials	Re-enter credentials
ERR_API_002	Insufficient permissions	Check exchange key permissions
ERR_API_003	IP restriction violation	Add server IP to whitelist
ERR_API_004	Rate limit exceeded	Wait 60 seconds, retry
ERR_API_005	Exchange unreachable	Check exchange status page
ERR_BOT_001	Insufficient balance	Check exchange balance
ERR_BOT_002	Configuration invalid	Review and reset settings
ERR_BOT_003	Trading pair unavailable	Check pair availability on exchange
ERR_BOT_004	Max positions reached	Normal — wait for positions to close
ERR_BOT_005	Strategy signal error	Contact bot author
ERR_SYS_001	Platform maintenance	Wait and retry
ERR_SYS_002	Data sync error	Refresh dashboard
ERR_AUTH_001	Session expired	Log in again
ERR_AUTH_002	2FA required	Complete 2FA verification
ERR_AUTH_003	Account suspended	Contact support

---

Summary

Here’s everything we covered in this guide:

1. API connection errors — Invalid API Key, Insufficient Permissions, IP restrictions, timeouts
2. Bot activation problems — indefinite connecting, immediate stops, activation failures
3. Trade execution problems — no trades executing, wrong prices, stop loss and take profit not triggering
4. Performance and configuration issues — below-average returns, unexpected drawdown, inconsistent position sizes
5. Dashboard and display problems — balance discrepancies, missing trade history, chart display failures
6. Account and login issues — login failures, unauthorized activity response
7. Notification problems — email, push, and Telegram troubleshooting
8. Exchange-specific issues — Binance, Bybit, and OKX specific error codes and fixes
9. Mobile app issues — data discrepancies and app stability
10. Complete guidance on when and how to contact support