KIRATroubleshooting
Keep the exact error, the Kira ID, and every public transaction link. They are enough to identify where an action stopped.
Chart is empty or behind
Confirm the full token address and compare Kira's latest trade with the explorer. A chart may open from saved candles while older history fills in. It should continue receiving new trades even if one historical transaction cannot be decoded.
If the tape moves but the candle does not, send support the first missing transaction. If both stop while the explorer moves, include the token address and project link.
Holdings or PNL look wrong
Archived and regrouped wallets still count toward PNL. Transfers between managed wallets do not. For a closed position, compare total sold minus total bought. For an open position, add the current holding value.
If a wallet shows tokens but cannot sell, check whether an earlier sell is still pending and include the wallet address and transaction when contacting support.
Launch or bundle did not finish
Creation and bundle entry are separate results. Open the Launch job and keep the token address plus every displayed transaction. Bundle later and 5 candidates can be waiting by design; a failed wallet or launchpad check should show a clear failed state instead of remaining on Launching forever.
Do not start another launch from the same prepared project while the first result is unknown.
Private order did not finish
Open History and keep the order ID, source deposits, bridge transaction, and final destination. Do not send the same deposit twice. If the order is not completed, send those references to support.
Claim, dust, or positions scan is slow
Large wallet sets run in batches and show progress. Leave the scan open instead of starting several copies. If execution stops, keep the completed transaction links and the list of wallets still shown as skipped.
What support needs
- account username;
- active chain;
- project, launch, campaign, or order ID;
- full token address;
- public transaction links;
- exact error text and screenshot.
Never send a private key, login credential, browser session, or provider key.