Fix a stuck action or disabled button

A transaction was already sent

1. 1

   Open Transaction details

   Copy the transaction hash and check it in the explorer for the same network. Also look at your wallet’s activity.

2. 2

   Let confirmation finish

   Aurora checks recorded transactions automatically. These checks do not spend gas or need another wallet approval.

3. 3

   Use the available recovery controls

   Refresh status or supply the existing hash when the interface offers it. If the wallet outcome is uncertain, check activity before deciding that nothing was sent.

A button is disabled

The wallet approved, but setup is not finished

Some controller and release flows use several transactions. An approval can finish just one step. The progress window shows an estimated step count, such as Step 2/4, and the remaining approvals. Keep the window open and read each transaction before confirming.

Pause and close stops the guided flow from advancing to later approvals. It cannot cancel a transaction already sent. Check any pending transaction, then use the available Continue action to resume the remaining setup. Do not start a second controller setup while the first is pending.

Max or your mint allowance is slow to load

The Max shortcut loads your remaining allowance in the background and retries temporary failures automatically. While it is unavailable, enter the quantity you want and use Review mint. The review checks the exact allowance, price and remaining supply before asking your wallet to confirm.

If review rejects the quantity, reduce it and review again. A known zero allowance, a closed phase, unavailable fee pricing or incomplete CAPTCHA can still prevent minting. Refreshing should not be needed just to restart a slow Max lookup.

Mint availability changed or the transaction reverted

On older collections, another collector can mint after you review and make your approval out of date even when NFTs remain available. New concurrent mint collections assign artwork when your transaction executes, so another wallet minting does not invalidate your approval. Supply and wallet limits still apply, the same wallet minting again invalidates its earlier approvals, and approvals expire after two minutes. Aurora checks the transaction again before opening the wallet. If that check stops, select Review mint again and complete a new CAPTCHA if requested; nothing was submitted by that check.

The check does not reserve your mint while the wallet is open. If the wallet warns that its simulation failed, cancel the request and start a fresh review. Do not confirm a transaction that the wallet says will fail.

If a transaction was sent, check its receipt before retrying. A confirmed revert creates no NFTs and reverses the mint payment, but can still cost network gas. If it is pending or the result is unknown, keep checking that transaction instead of submitting another.

You cancelled a wallet settings request

Rejecting an unsent trading or royalty change lets you return to the settings and review the choice again. If the wallet may already have submitted a transaction, check its activity and the recorded hash first. A pending transaction must be resolved before you start a conflicting change.

A mint looks upcoming but cannot be minted

A coming-soon preview is not an open sale. A closed release stays closed even if a later phase date is entered. The creator must complete the appropriate release action. Directory information can also take a short time to refresh; the mint page checks current availability.

Information to include when asking for help

Never send a wallet recovery phrase, private key or unrelated account secrets. Use the official Aurora X profile linked from the site to find the current public contact channel.

• The page URL and the action you were trying to complete.
• The network, collection address and transaction hash, if one was sent.
• The exact error and a screenshot with private information removed.