Start with the Bot’s reply and the portal’s request activity. A generic error message alone does not identify its cause.
Common problems
When is it appropriate to retry?
Awaiting correction
Nothing submitted
Pending or unknown
Reply directly to the current launch correction prompt. Do not start another complete launch merely to supply a missing field. A request allows up to two guidance or correction replies in total; help and template follow-ups can consume those replies too.
Fix the stated cause first. If the request is closed and the Bot explicitly confirms nothing was submitted, send a complete new launch request with its own image. It may be in the same conversation.
Do not repost or assume failure. Inspect the request and any transaction link, and wait for its outcome to be resolved. An unknown submission might already have reached the chain.
A new Post is a new request and can create another token. Reusing a name or symbol is not a deduplication mechanism.
Help and template follow-ups
A template is an example, not a saved launch draft. After requesting it, send a complete launch instruction with your own fields and one supported image. Replying only Symbol: FIX does not adopt the other sample values.
V1 currently counts help and template messages toward the same three-Post classification limit when they continue one request. After two guidance or correction replies, a third incomplete message can close the request without a final explanation. This is a known limitation, not evidence of an X delivery failure.
If you only asked for help and supplied a partial field, use a complete launch request when ready. If you also sent a complete launch or saw a pending submission, check its status before reposting. Do not infer a failed transaction from silence.
Standalone buy, sell and withdraw guidance uses a separate path and does not use up the active launch’s correction attempts. It still respects reply limits and opt-out. See guidance behavior.
Launch succeeded, but I do not see tokens
Creating a token does not allocate the initial supply to your wallet. Without a Dev Buy, the supply goes into locked liquidity.
If you requested a Dev Buy, check the confirmed transaction and the smart account’s token balance, not only the Owner wallet. Use the contract address to identify the token. A delayed asset list or missing reply is not proof that the purchase failed.
See Verify the purchase before retrying.
Activation or deposit failed
Check the selected network, connected Owner wallet, wallet rejection messages and available Base ETH for gas. An HTTP or RPC error does not by itself mean an X permission or API-key permission is missing.
If a transaction was sent, inspect its receipt before repeating setup or a transfer. A successfully activated smart account does not need to be recreated just because a later request fails.
What to include in a support report
Share the Post URL, approximate time, Base smart-account address, displayed error, request status and transaction hash if available. Explain whether the request included Dev Buy and its amount.
Do not share private keys, seed phrases, API secrets, authentication headers or private RPC URLs. Use the official community channels for help. 