Submissions

• Progress. While a phase runs, the row shows the time since you submitted. Once the platform has accepted the request, the row also shows “Step n of 6”. The six steps are preparing, signing, submitting, confirming, indexing and “Complete”, and awaiting approval shares the signing step. Where the platform reports them, the row also shows the confirmations counted against the number required, such as “2/12 confirmations”, and how many blocks the indexed view runs behind the chain. A mint, burn, transfer or forced transfer started in this browser tab names the amount it moves under the asset, such as “10 BND”.
• Waiting labels: Awaiting approval means an approver holds the request. It reads “Awaiting” followed by the provider's name and “approval” when a custody provider holds it. The name is the provider the custody configuration was added as, so a request held by a configuration added as IBM Digital Asset Haven reads “Awaiting IBM Digital Asset Haven approval”. A held row also shows when the approval expires and, when the provider reports a count, the approvals it has counted against the number it needs, such as “1 of 2 approved”, in the language of the page. Once the deadline has passed at a provider that cannot withdraw the request, the row says the request is still open there and must be rejected in the approval console of that provider. “Waiting for funds” means the wallet that pays for the request cannot cover the fee. The request continues on its own once the funds arrive, as Transaction funding describes. “Recorded on-chain” means the platform is rebuilding its indexed data and your lists catch up on their own.
• Details: Details opens the submission's details sheet. While the platform is still working on the request, its “Current status” and the line under its title read the same as the row, such as “Awaiting” with the provider's name and “approval”, or “Cancelling” after you asked to withdraw a held request. Once the platform reports the request complete, the sheet reads “Completed”, also while the row still shows “Indexing”.
• Cancelling: the tray offers Cancel from the moment the platform accepts the request until it confirms, except while you sign it in your wallet. An operation that offers “Undo” shows “Undo” instead. A dialog states the cost before you confirm. Before the request reaches the network, nothing has been sent and cancelling costs nothing. After it is sent, a replacement transaction cancels it, and that costs gas. For a request that a custody provider holds, the platform withdraws the approval request at the provider, and the tray offers “Cancel” only where the provider supports that. The platform can still refuse a cancellation, and the message then starts “Could not cancel.” and gives the reason. Transaction lifecycle explains the replacement.
• Server adjustments: the Console can show a result before the chain confirms it. When the confirmed record differs, the settled row lists the fields that changed under Adjusted by the server. The marks stay visible when your system asks for reduced motion.
• Failures. A failed row names the next step: “Try again”, “Edit and retry”, “Top up and retry”, “Top up and edit”, “Check status” or “Contact support to resolve.” When the platform cannot tell whether a submission went through, the row reads “Outcome unknown” and the details sheet tells you not to retry until the outcome is confirmed.
• May still go through. The platform stopped waiting for the request, but a custody provider still holds it or the network may still include it. The row shows no step and says not to try again until you have checked the request in the custody provider console or on the network. Where you may read it, the row and the details sheet show the platform's reason in English. When the platform settles the request, the row moves to Complete or Failed. If the row has not changed, open “Details” to read the latest status.
• Several operations. Two or more submissions of the same action, such as several mints, collapse into one expandable row named after that action, with a count for each phase. A different action, such as “Create asset”, keeps its own row and never counts toward another action's row. A page refresh keeps in-flight work in the same browser tab and checks each operation against the platform's status. Other open Console tabs show the same phase. The operation you started last follows its status live. Any other submission still in flight checks its status every 10 to 15 seconds, so many pending submissions never slow the rest of the Console. Screen readers hear each phase label once, as a polite announcement, and the elapsed time is not announced.

Troubleshooting#