Common Error Messages

Most platform errors tell you two things: what happened and what action you should take next.

Start with the simple message shown on screen. If the issue is about one trade/order, also open Orders and copy the Leg Ref, broker, symbol, and approximate time. Analytics has full IDs if support asks for them.

This means the page contains private account data or live action and you are not signed in.

Click Login, complete password and 2FA if enabled, then open the same page again.

The selected tool is not active for your account.

Use Payment if you need to purchase/renew. If you already paid, check email for payment confirmation and then check invoice/payment status in Settings. Contact support if access did not activate.

This means the platform did not find any enabled app access for your account.

If you are a new user, subscription or trial setup may not be complete. Contact support with your registered phone/email.

This means your platform login session or broker session is no longer valid.

For platform session, login again. For broker session, reconnect the broker from Settings. Many broker sessions must be reconnected regularly.

Your subscription may be active, but broker session is not connected.

Open Settings, confirm the correct assigned broker card is visible, save credentials if needed, and click Connect or Reconnect.

This usually means API Key, API Secret, app key, token, or broker setup details are wrong or expired.

Open Settings, edit the assigned broker account, update the allowed credential fields, save, and reconnect. Client ID/User ID cannot be edited by the client.

Some broker APIs require the Bluechip Algos static IP to be whitelisted in the broker API portal.

If the broker rejects login/order because of IP, add the static IP given by support in the broker portal and in Settings. If you do not know the static IP, WhatsApp 9398840360.

Connect/Reconnect may open the broker login page in a popup or new browser tab.

Allow popups for this site, then click Connect/Reconnect again.

These are reference numbers used to find the exact problem quickly.

Orders keeps the client view simple and shows Leg Ref with the status and message.

Analytics can show the fuller reference context when support needs Trade Ref, Order Ref, or Broker Order ID.

For order-related support, share app name, broker, symbol, approximate time, Leg Ref, and the exact message shown in Orders.

The broker or platform rejected the order.

Open Orders and read the leg row message. Common reasons are insufficient funds, invalid quantity, expired broker session, wrong contract, market closed, or exchange/broker rejection.

This means the broker did not allow the order because available funds or margin were not enough.

Add funds, reduce quantity, change product type if appropriate, or avoid the trade. Example: If you try to BUY an option at Rs 100 with Qty 10 and broker margin is not enough, the order can be rejected.

This means the order quantity is above the exchange or broker freeze limit.

Reduce quantity or split the trade where supported. Example: If the allowed maximum is lower than your order quantity, broker can reject it.

Live trading needs fresh market data such as LTP/reference price.

If fresh price is unavailable or stale, the platform blocks or fails the action instead of using unsafe old price. Wait for market data to recover and check the order again.

This means the app or broker could not resolve the exact instrument.

Check symbol, segment, expiry, strike, CE/PE, and whether that contract is currently valid/tradable.

This means the order or signal came outside the allowed trading window.

Check strategy start time, end time, entry time, exit time, and market hours. Example: A strategy that allows entries only until 09:30 should reject a new entry at 09:45.

This means a strategy, signal, leg, global switch, kill switch, or account control blocked the order.

Check the app dashboard controls before expecting new orders. If a switch is off, the app should not fire live orders.

Cancelled means the order was stopped before full completion.

It may be cancelled by the broker, platform, or user action. Check whether any partial fill happened before assuming the full quantity was cancelled.

Share app name, broker, symbol, strategy name if any, Leg Ref, error message, and approximate time. Analytics has fuller IDs if support asks for them.

This helps support trace the exact event without asking for private credentials.

Do not share platform password, broker password, OTP, authenticator code, API Secret, TOTP secret, full broker token, or full webhook token.

If support needs setup help, use official WhatsApp 9398840360 and share screenshots only after hiding private secrets.