Unblock a proof
What to do with a proof awaiting license, pending review, failed or rejected.
A proof that does not reach Certified stops on one of four statuses. Each one has its own cause and its own way out. A message shown on the agent's screen during a session is explained in the agent's Troubleshooting page.
Awaiting license
The proof is valid, but your organization had no license left when it was checked. It is kept, not refused, and listed in the Awaiting license block of the Proofs page.
You do not need to upload it again. As soon as licenses are available to your organization, the portal certifies the waiting proofs on its own.
- Client admin: allocate licenses to the organization concerned from the Licenses page. If you have none left to allocate, contact your provider for a new license grant.
- Technician: tell your client admin.
Pending review
The agent could not tell what kind of machine it erased. The portal needs this information before issuing the certificate, so it parks the proof in Pending review. No license is used while it waits.
Open the proof
In the History table of the Proofs page, filter on the Pending review status and click View.
Set the machine type
In the Pending review block, choose the Machine type: Desktop, Laptop or Server. Then click Set machine type.
Processing resumes right away. Your name is recorded as the reviewer, and the machine type you chose appears on the certificate. Client admins and technicians can do this.
Failed
A temporary problem on the portal side (a service unavailable for a moment, for example) interrupted the processing. It is not a problem with your proof.
The portal retries on its own, several times, with a growing delay between attempts. Most failed proofs are certified this way without any action.
If a proof is still Failed after that, it appears in the Recovery block of the Proofs page, with the step that failed. A client admin can click Retry to put it back in the queue. This is a sensitive action: the portal may ask you to confirm your identity.
If retrying does not help, contact your provider's support with the proof identifier. Support can restart the processing from the beginning or, if the proof cannot be certified, abandon it with a reason.
Rejected
The portal does not retry a rejected proof on its own. The proof page shows the reason. A client
admin can retry it through the portal's API, POST /api/v1/proofs/{id}/retry (the Retry button
of the Proofs page is for failed proofs only). Retrying helps when the cause was on the
portal's side, such as an enrollment or a setting fixed since; when the cause lies in the proof
itself, it gives the same result. The most frequent reasons:
| Reason | What it means | What to do |
|---|---|---|
| No successful disk | No disk of the session reports a successful erasure: there is nothing to certify. | Check the disks and run the erasure again. |
| Duplicate session | This wipe session already led to a proof in your organization. | Look for the existing proof and its certificate. If there is none, send the logs for support: see Contact support. |
| Organization mismatch | The proof was produced for another organization. | Upload it in the right organization's portal. |
| Identity refused | The agent that produced the proof is unknown to the portal, or was revoked. | Once the ISO's enrollment is fixed, a client admin retries the proof. If the ISO was revoked, run the erasure again from a new issued ISO. |
| Untrusted signer | The proof was not signed by a trusted Wipe agent. | Use only the agent downloaded from the portal. |
| Unknown schema version | The agent is too old, or too recent, for this portal. | Use the agent version offered in Settings → Agent & tools. |
| Signature missing, Invalid signature, Invalid envelope | The file is damaged or was modified after the erasure. | Upload the original file again. If it fails again, contact support. |
| Report digest mismatch, Session binding mismatch | The content of the proof does not match its signature. | Upload the original file again. If it fails again, contact support. |
| Payload not JSON, Invalid payload, Schema validation failed | The agent produced a proof the portal cannot read. | Update the agent and contact support with the proof identifier. |
| Stored hash mismatch | The stored file no longer matches the file received. | Contact support. |
A client admin can be notified of failed, rejected or license-blocked proofs through a webhook.