Diagnose and resolve

Troubleshooting

Resolve common workflow, scoring, import, evidence and access issues.

Cannot log in or complete 2FA
  1. Confirm the email address and reset the password when necessary.
  2. Set the authenticator device to automatic date and time.
  3. Use an approved backup code if available.
  4. Record the complete error before contacting support.
A document is not visible to the approver
  1. Confirm that Submit for Approval was used rather than Save as Draft.
  2. Verify the selected approver and their active role mapping.
  3. Check the approver Pending Approval tab and notifications.
  4. Confirm that the document was not recalled.
A document cannot be published
  1. Confirm that it is approved.
  2. Complete a mandatory quiz where configured.
  3. Select an audience permitted for the document type.
  4. Choose today or a future publication date.
A scheduled document did not publish
  1. Confirm the scheduled date and organisation time zone.
  2. Verify that the document still has an approved status and valid audience.
  3. Check notifications and the Scheduled tab for an error state.
An asset import failed
  1. Use the current sample CSV and preserve required headers.
  2. Remove blank rows, invalid dates and duplicate identifiers.
  3. Confirm owner and custodian users exist and are active.
  4. Test a small sample before a large import.
The asset value looks wrong
  1. Recheck confidentiality, integrity and availability values.
  2. Confirm whether the organisation uses a 3×3 or 5×5 scale.
  3. Review asset value bands and recent administrator changes.
The asset does not appear in the Risk Register
  1. Confirm required CIA values are complete.
  2. Use Assess Now and wait for the success result.
  3. Clear Risk Register filters and refresh.
  4. Confirm your role can access the target risk record.
Risk controls do not load after selecting a domain
  1. Confirm the selected framework has controls in that domain.
  2. Verify the control source is active and accessible.
  3. Refresh the assessment and retry the selection.
  4. Capture the risk ID, framework, domain and browser console error for support.
The qualitative score looks wrong
  1. Distinguish initial asset value, inherent, current, residual and target scores.
  2. Recheck likelihood, current controls and uncertainty.
  3. Confirm the correct matrix and acceptance criteria.
  4. Do not treat planned controls as already operating.
The assessment cannot be completed
  1. Check whether residual exposure remains above appetite.
  2. Add or strengthen treatment, or raise an exception.
  3. Confirm required fields and controls are saved.
  4. Review the summary for incomplete stages.
The assessment cannot be edited
  1. Check whether an exception decision is pending.
  2. Wait for the approver to approve or reject the request.
  3. A rejected exception will reopen the assessment.
FAIR results appear unrealistic
  1. Confirm the scenario covers one specific threat.
  2. Recheck annual frequency versus per-event values.
  3. Review vulnerability probability and loss magnitude ranges.
  4. Document uncertainty rather than forcing narrow estimates.
A control marked Not Applicable will not save
  1. Enter a meaningful justification.
  2. Confirm required applicability and status fields.
  3. Check your control-owner or compliance permissions.
The compliance score did not update
  1. Save the control or evidence record.
  2. Review the improvement drivers for incomplete requirements.
  3. Confirm evidence is linked to the correct control.
  4. Refresh the dashboard after the underlying status is updated.
A user has incorrect access
  1. Review the organisation role and its system-role mapping.
  2. Check group and module assignments.
  3. Test with a fresh login after saving changes.
  4. Use least privilege and remove conflicting mappings.
Escalate with evidence

Still blocked?

Include the module, record ID, affected role, timestamp, expected and actual result, steps to reproduce and complete error text.

  • Remove passwords, tokens and secrets.
  • Use sample data where possible.
  • Attach screenshots that show the full workflow state.