01

What you are doing

You are separating account, permission, funding, subscription, runtime and notification problems instead of changing multiple controls at once.

02

Why it matters

Blind retries can create duplicate payments, unsafe API permissions or conflicting bot states.

03

Before you start

Record the visible error, timestamp, bot and current Bybit position state. Never include passwords, API secrets, QR codes or seed phrases in a support message.

04

Step by step

  1. 01Check the platform last-update time and health state.
  2. 02Verify membership.
  3. 03Verify the dedicated subaccount balance.
  4. 04Verify API key status, environment, IP whitelist and required permissions.
  5. 05Check bot status and whether an open cycle is being drained.
  6. 06Check Telegram connection only after the underlying event stream is healthy.
05

What you should see

The failing layer should have a specific error and a contextual Help link. Fix that one layer, then rerun its validation.

06

Security check

SECURITY CHECK FAILED is not bypassable. Recreate the key with the minimum allowed scope.

07

Common problems

I cannot create an API key

New Bybit accounts may have a temporary restriction. Follow the exchange message.

HEDGERON says the key is unsafe

Use a dedicated Standard Subaccount key with no Withdraw or unrelated sensitive permissions.

HEDGERON says the key cannot trade

Enable Contract Order and Position permissions.

Payment is still pending

Do not send a second payment immediately. Check confirmations and invoice status.

Telegram alerts stopped

Check the connection, blocked-chat state and event-stream health.

Dashboard data looks stale

Use the last-update timestamp and health status; do not trust a stale green indicator.

Bot is ACTIVE but no trade is open

This can be normal while the engine waits for valid conditions.

08

Next step

If the issue remains, contact official support with the error code and timestamp, but no secrets.