Troubleshooting

Start by checking the connected address, network and action's receipt. Then identify whether you are waiting for a read, a signature, a transaction, a fill, a Window result or a claim. Those are different stages.

I have tUSDC but cannot trade

Check STT as well: it pays the testnet transaction fee. Confirm Somnia Shannon is selected and that the chosen funding pool has available funds.

A balance in Private, Earn or a strategy grant may not be available to an ordinary wallet ticket. Open your money breakdown to find the pool.

Get test funds did not finish

• Waiting for a refill / allocation used up: use an external STT faucet from the panel. If the wallet already has sufficient gas, the tUSDC mint can continue.
• Wallet cooldown: the next gas request time is shown. Moving STT away or clearing browser storage does not reset it.
• STT confirming: open the displayed transaction link. Retrying checks the same saved transfer. An unknown transfer is not a confirmed failure.
• STT arrived, then I cancelled: the gas stays in your wallet. Choose Get test funds again and confirm the tUSDC mint when ready.
• tUSDC mint unknown: check that transaction before submitting another mint. The gas-service recovery guarantee applies to the STT transfer, not to arbitrary new wallet transactions.
• Balance unavailable: wait for the read or retry. No new STT allocation is made when the required balance or quota cannot be checked.
• Needs operator review: the recorded funding transaction conflicts with chain evidence. Use an external faucet while the operator investigates; repeated clicks do not create a replacement transfer.

See wallet setup for the two prompts and current limits.

The ticket is blocked

Read the button's first reason. Common conditions are a missing opening print, an entry cutoff, an invalid amount, insufficient balance, a price beyond your allowed ceiling, or no usable liquidity.

If a Window is too close to its end, pick the next suitable one. If the ticket automatically advanced, reread its expiry and notice. If the book is thin, a smaller amount or another Window may be possible; repeatedly signing does not add liquidity.

The wallet says submitted but there is no position

Submission is not a fill receipt. Open the transaction link and check the app's final result. Nothing filled means the attempted order did not obtain a position. Unknown means the app has not established the outcome yet.

Wait for a definite outcome before sending the same order again. A reverted chain transaction can still cost gas, even when the requested trade or deposit did not complete.

An error appeared after I approved or deposited

Multi-step actions can partially complete. Strategy joins, cap changes, X top-ups and some withdrawals may use several transactions. An error in the last step does not reverse earlier confirmed steps.

Check the pool balance, token approval, grant and subscription states relevant to that action. Use the available receipts to complete the missing step rather than automatically depositing the whole amount again.

The timer ended but I have no winnings

The Window still needs its final oracle result and the product's settlement. A winning result can then need collection.

Use the right screen: ordinary/Lucky wallet calls in Portfolio; Range and Moonshot under Your rounds; Parlay under Your tickets; Duel on its match result; Private under its claim list. See Portfolio's collection table.

If a claim batch only partly succeeded, use Claim the rest for the outstanding items. Do not assume a timer reaching zero sends every payout to your wallet.

My browser key is missing or the session expired

For ordinary tap-trading, connect the owner wallet and use Re-key. Check expiry, remaining budget, daily headroom, open-Window cap, price ceiling and key gas if the key exists but buys are blocked.

For a Duel, reopen its match link and use Name this browser's key when offered. A general session replacement and a match-specific replacement are different permissions.

Forget this key removes local data; Revoke stops the chain permission. Revoke a key you no longer plan to use before forgetting it.

An agent is published but not trading

Check these in order:

1. Is the runner configured and recently reporting health?
2. For AI, can its model answer? A missing credential is different from an intentional hold.
3. Does the strategy have a current funded grant and active subscription?
4. Is there a suitable live Window and sufficient book depth?
5. Do the requested orders fit the creator's envelope and follower's limits?
6. Does memory say held, sent, filled, or something unknown?

Check for confirmation unknown or unavailable execution/risk records too. An unresolved runner transaction holds further submissions while its receipt is checked. Restarting the worker or increasing a budget does not resolve that evidence. A cooldown follows actual settlement time and survives restarts.

Copying enabled describes permission. Read the separate Operation: Awaiting settlement can mean your open-position limit is full; a daily-limit hold resets at 00:00 UTC. Filled or held counts in a runner report cover all subscribers. Expand the timestamped report and inspect your own transaction receipts.

If publication reports insufficient native gas, use the displayed available balance and minimum for that exact step. Fund gas, then retry the retained draft. A known transaction whose outcome is uncertain still needs inspection before another publication.

Publication proves the registry record exists. It does not start a self-hosted process. Follow self-hosting if you selected your own bot wallet, and copy management for funding/subscription recovery.

X points to a different wallet

Use X recovery to reveal the binding. Connect the original owner wallet to manage its money.

To change the linked wallet, first connect the original owner and Disconnect X from its account controls. The current server refuses a new link while the account is still bound elsewhere. Then connect and link the new wallet. This changes future routing; it does not move funds held by the previous wallet. X Cash out releases unspent grant budget to Trading Balance, after which Withdraw moves available funds to the owner wallet.

An X reply is missing or needs checking

Open Trade from X and find the original instruction's receipt before posting it again. A missing reply or image does not tell you whether the trade was sent.

Read Mentions, Orders and Replies separately. A healthy poll cannot establish a successful trade or image upload. Missing or old checks stay unverified or out of date. The last acknowledged image time refers to a completed media reply, not necessarily your instruction.

Status needs checking means the result is uncertain. If there is a transaction link, open it for the latest chain result and compare it with the app. Without a link, check the app and report the instruction and approximate time if the outcome remains unclear. Do not assume the trade failed or that another copy is safe to send.

The relay can recover an interrupted execution from matching chain evidence without placing it again. A public post whose acknowledgement was lost remains held for inspection; execution recovery does not automatically repost it. An operator should inspect the original mention before deciding how to recover the reply.

Repeated bot replies can be a reply-loop defect even when only one trade occurred. Check the original receipt and contact the operator. Reply posting can be disabled independently of order execution. The release safeguard excludes the bot's own replies and known receipt ids before they can become commands.

Order filled means a position was booked, not that the Window was won. Spent is its recorded cost; a Requested amount alone does not establish that cost. See how to read X receipts for each status.

A game has no opponent, deck or score

Practice: it needs readable live Windows and prices. No suitable deck can simply mean there is not enough time left in the current Windows.

Duel: leave the queue if you do not want to wait. If already entered, resume the existing match instead of treating the queue as the record of the match. Its deadlines continue while disconnected.

Arcade: a run can remain local if you are signed out, the identity service is unavailable or no score store is configured. The game can still play. A board error does not turn the score into an on-chain record.

Leaderboard keeps reading data

Reading on-chain trade data… can persist while the provider or history scan is slow. Metric dashes mean the values have not been read; they do not mean zero traders, zero stake or no trades.

Check the displayed scope and Status, then retry when reads recover. If the page still cannot load, report that loading state rather than presenting an empty table as a completed ranking.

I cannot restore private claims in a new browser

The empty-claims screen now offers Restore. Connect the owner wallet, choose Restore and import its signed backup. Invalid signatures or malformed JSON are refused; duplicate claims are ignored and another owner's claims are not added to your list. Wallet reconnection alone does not recreate the backup. Keep the original export private.

What to include in a useful issue report

Share the page, approximate time, displayed message, network and public transaction or match link when relevant. Explain the last completed step and whether the wallet showed a confirmed transaction.

Do not publish wallet secrets, browser keys, private claim JSON or provider credentials. A screenshot can omit those while retaining the error and public receipt needed to investigate.