Items awaiting minting

The minting jobs that still carry pending items, with the batch they came from when there is one.

On this page

An item awaiting minting is a row that has been prepared but whose token has not been created on-chain yet. This screen shows which jobs those items belong to. You reach it from the "Awaiting minting" entry of the Catalog section, or by clicking the amber counter in the header bar.

#What the screen shows

A table, one row per minting job carrying at least one pending item, newest first.

Eight columns: the job number, the prepared product, the brand, how many items are still waiting, the job status, the production batch, the creation date and a "Cancel job" button.

The Production batch column carries a link to the batch page when the job is attached to one. It reads "No batch" otherwise: a job created outside a batch has no page to go to, and the screen says so rather than offering a link that would lead nowhere.

When nothing is waiting, the table reads "Nothing is waiting to be minted."

#What you can do here

Open the batch page of a job that has one, to follow its encoding there.

Give up on a job you no longer want, with "Cancel job". A dialog asks for confirmation before anything is sent. Its still-waiting items move to failed with the reason manual_cancel, the job itself moves to failed, and it leaves this list as it leaves the header counter. Anything already written or minted is left untouched.

This is the same action offered on a batch page, and it goes through the same route. Nothing is erased from the database: the job stays readable and the cancellation is written to the audit log with its author.

This screen starts no minting.

#What access requires

A signed-in administrator account. The jobs shown are limited to the brands the account can access, a scope applied by the server; an account with no accessible brand gets an empty list.

#What the screen refuses

A cancellation never goes out on a single click: the confirmation dialog is mandatory.

A job that is no longer in flight, meaning already finished, failed or already cancelled, is left alone. The server answers without changing anything and the list stays as it was.

A job belonging to a brand outside your scope is refused by the server.

Two useful remarks. The header counter counts items awaiting minting, and those only. Items already minted that are waiting for their chip to be written are elsewhere, in the product list, under the "To encode" button.

This screen stays reachable from the menu even when nothing is waiting, while the header counter disappears in that case. That is deliberate: without this entry, you could not check that nothing is waiting, only learn about it when something is.

Your answer opens a pre-filled email in your mail app, addressed to contact@sealtrust.io. You read it over before sending it.

Suggest a correctionReport a problem