Skip to main content
Version: 1.0.0-beta

Troubleshooting — Findings

I can't create a finding

CheckSolution
Your role has finding:create permission?You need Auditor, Manager, or CAE role
You selected an engagement?Findings must be linked to an engagement
The engagement is in Fieldwork or later?Findings can only be created during active engagements

Finding won't move to FINAL status

  • Findings can only be finalized by Manager or CAE roles
  • Ensure all required CCCER fields are filled (at minimum, the Condition/description)
  • Check that a management response has been recorded

AI Draft Finding gives poor results

  1. Provide more context — ensure the workpaper has detailed test procedures and results
  2. Check the AI model — verify a model is configured in Administration → AI Models
  3. Be specific — the AI generates better findings when the workpaper conclusion is clear
  4. Review the confidence score — low scores indicate insufficient context

Action plan owner can't update their plan

  • The action plan owner must be logged in with the account matching the owner_id
  • Self-service updates are limited to marking as "Implemented" and uploading evidence
  • Status changes to Verified or Closed require audit team action

Remediation evidence upload fails

ErrorSolution
File too largeMaximum 50MB per file
Unsupported formatPDF, Word, Excel, Images, ZIP supported
Virus detectedFile was flagged — do not upload
Permission deniedOnly the action owner, auditor, or manager can upload

Finding versions are missing

  • Versions are created automatically on every edit — check the Version History tab
  • If no versions appear, the finding may have been created in a single session without intermediate saves
  • Versions are immutable and cannot be deleted

Escalation emails not being sent

  1. Check Administration → Notifications — ensure email notifications are enabled
  2. Verify the action plan is actually OVERDUE (past due_date with status OPEN)
  3. Check the email service configuration (SMTP settings)
  4. Review the audit log for notification events