Troubleshooting
Recover from common Knotest setup and Evaluation problems without weakening the record.
Application does not become ready
Use Retry when the startup screen reports a recoverable runtime failure. If automatic starts have stopped after repeated failures, use the offered recovery action before relaunching the application. Export a Support Bundle when the diagnostic repeats.
Do not delete application data or a Project as a first recovery step.
License problems
| Client state | Meaning | What to do in Knotest |
|---|---|---|
| Missing | No activation request has been submitted | Open Settings > License, complete the three required fields, and choose Submit request |
| Pending | Waiting for approval | Use Check to retrieve the latest status; keep the Request ID if you need support |
| Active | This installation has a usable lease | Continue; inspect Granted packs if a particular action remains unavailable |
| Refresh required / Expired | The local lease needs renewal | Connect to the internet and use Refresh |
| Update required | A newer grant is available | Use the offered Check or Refresh action and follow any client update message |
| Denied | The request was declined | Read the Decision note and contact your license administrator with the Request ID |
| Revoked / Suspended / Contract ended | Licensed access is no longer usable | Contact your license administrator; repeatedly submitting the same details will not resolve the underlying access issue |
| Clock invalid | The system clock moved backwards | Correct the computer's date and time, then retry |
| Invalid / Uncommissioned | The lease or installed build cannot be verified | Record the exact message and application version for support |
If Submit request is disabled, check Organization, Contact name, and Contact email. All three are required and the email must be valid. A connection error is separate from an approval decision: restore connectivity and retry the existing action before creating another request.
A copied Project does not activate another computer. Submit the request from the installation you intend to use. See Activate Knotest for the completed client form.
Dataset import failed
Open the retained activity under Datasets -> Needs attention or the Runtime monitor. Read its diagnostic, correct the external source, and begin a fresh import. Dismissing the activity hides it from active UI lists but does not turn the partial attempt into a Dataset.
Model is not ready
Confirm the backend, task, class order, input contract, and output interpretation. Then review Settings > Model inference for a compatible installed engine, device support, and recorded consent. Changed Model bytes must be imported again; Verification does not restamp them.
Prediction Generation is Missing or Failed
Missing is readiness, not execution failure. Follow the readiness messages to supply the required Dataset, Inference Source, settings, engine, or transform coverage. For Failed, open the retained diagnostic and start a new attempt after correcting the cause.
Evaluation cannot start
The selected Prediction Set may not contain the Evidence coverage required by the chosen module, transform, or severity. Generate a new set with that coverage or choose a compatible Evaluation configuration. A previously Ready setup is revalidated when you start the Evaluation.
A score is unexpected or a comparison is N/A
Check these in order:
- Confirm the Dataset split and sample count. The Helmet tutorial uses only 100 random Validation samples (seed 42); it is not a benchmark for general model quality.
- Check class order, model input dimensions, and prediction thresholds.
- Confirm the clean and transformed branches use matching sample coverage.
- Expand the metric and read its availability reason and configured criterion.
A negative degradation value means improvement for that comparison. A blank criterion can produce N/A even when a measurement exists. Unavailable data, a zero baseline that changes, and mismatched sample counts must not be treated as passing results. See Metrics, Thresholds, and Robustness.
A restored Project does not verify
Keep the original and restored folders separate. Read the verification issue to identify missing or changed files, then restore a consistent copy from backup. Do not rename, edit, or regenerate sealed files just to match a recorded hash. Follow Back Up and Restore.
Evaluation was interrupted
An interrupted activity is not a completed Claim. Use the available recovery or rerun action after the runtime is healthy. Preserve any retained diagnostic Evidence and do not change terminal files manually.
PDF export is unavailable
Confirm all of the following:
- the Evaluation reached a terminal state;
- it produced a Robustness, Fairness, or Explainability report artifact;
- the active License includes report export;
- the report draft is valid; and
- the current preview finished building without a blocking error.
When no PDF report exists, a technical results package may still be available.
Still blocked
Export a Support Bundle after reproducing the problem. Include:
- the Knotest version, operating system, and selected model runner;
- the page and exact action that failed;
- the expected result and the exact visible error;
- the time of the failure and whether it repeats;
- the affected Project, Prediction Set, or Evaluation identifier when relevant;
- a screenshot and the Support Bundle, shared through your approved channel.
Use example data when possible. Do not include API credentials or upload an entire customer Dataset unless your support process specifically requires it.