Skip to main content

Error Messages Guide

Error Messages

This is a non-exhausting list of the most common UI error messages that can occur in the application, organized by page/module. Each error includes its translation key, user-facing message, possible causes, and suggested solutions.

📋 Overview​

Pages Covered (21 sections): 🔐 Login Page - 6 errors (authentication, rate limiting) đŸ‘Ĩ Users Page - 6 errors (CRUD, team assignment, validation) đŸ‘Ĩ Teams Page - 4 errors (CRUD, validation) 📊 Projects Page - 5 errors (CRUD, search, validation) đŸĸ Branches Page - 3 errors (CRUD, validation) đŸĸ Clients Page - 3 errors (CRUD, validation) 🏗ī¸ Zones Page - 5 errors (create/delete zones, ranges, config) 🔍 Zones GoTo Page - 1 error (navigation) 📱 Devices Page - 5 errors (CRUD, device groups, validation) 📱 Device Groups Page - 3 errors (CRUD, validation) 📋 Registrations Page - 8 errors (CRUD, roles, permissions) 📊 Scans Page - 11 errors (CRUD, verification, approval) 📋 Zone Sessions Page - 3 errors (CRUD, busy flags) 📋 Open Zone Sessions - 1 error (abort session) 📋 Planning Page - 13 errors (zone states, sessions, PDFs, transformations) 🔄 QM Module Page - 7 errors (approvals, jobs, data loading) 📤 Exports Page - 6 errors (job management, file operations) đŸ“Ĩ Imports Page - 5 errors (file validation, import processing) 💾 Database Page - 8 errors (generation, upload, device messages) 📊 Dashboard Page - 5 errors (charts, QR codes, preferences) 🔔 Notifications Page - 2 errors (resolve, assign) 🚀 Navigation (Project Lifecycle) - 12 errors (quotas, verification, state transitions) ℹī¸ Introduction Page - 1 error (content errors) ⚙ī¸ Settings Page - 1 error (update settings) 📋 Main Application - 9 errors (settings, files, jobs, access) ✅ Form Validation - 5 generic validation errors Total: 133+ documented errors organized by functional area! ✨ Key Features: ✅ Organized by Page/Module - Easy to find errors for specific features ✅ Translation Keys - Exact key for each error message ✅ User Messages - What users actually see ✅ Multiple Causes - All possible reasons for each error ✅ Actionable Solutions - Specific steps to resolve ✅ Error Categories - Grouped by type (permissions, validation, state, database, files, dependencies) ✅ Troubleshooting Guide - 7-step general process for any error ✅ Context & Notes - Error format patterns, variables, permission model

🔐 Login Page​

File: login.json

Username Required​

  • Key: login.error.username-required
  • Message: "Your username is required"
  • Cause: User attempted to log in without entering a username
  • Solution: Enter a valid username before attempting to log in

Password Required​

  • Key: login.error.password-required
  • Message: "Your password is required"
  • Cause: User attempted to log in without entering a password
  • Solution: Enter a valid password before attempting to log in

Incorrect Password​

  • Key: login.error.403
  • Message: "Incorrect password"
  • Cause: User entered an incorrect password for the given username
  • Solution: Verify credentials and re-enter the correct password

Username Length Validation​

  • Key: login.error.username-length
  • Message: "Username must be at least {{details.MinLength}} characters long"
  • Cause: Username entered is shorter than the minimum required length
  • Solution: Ensure username meets minimum length requirements

Unknown Error​

  • Key: login.error.unknown-error
  • Message: "Unknown error"
  • Cause: An unexpected error occurred during login process
  • Solution: Contact system administrator or try again later

Too Many Requests (Rate Limiting)​

  • Key: login.error.too-many-requests
  • Message: "Error, too many requests. Please slow down. You must wait {{details.timeToReset/1000+0.5|number:0}} seconds before trying again."
  • Cause: Too many login attempts in a short period (rate limiting protection)
  • Solution: Wait for the specified number of seconds before attempting to log in again

đŸ‘Ĩ Users Page​

File: users.json

Delete User Failed​

  • Key: users.error.delete.failed
  • Message: "Deleting the user failed. Error: {{error.message}}"
  • Causes:
    • User has associated data that prevents deletion
    • Insufficient permissions to delete users
    • Database connection issues
    • User is currently logged in or active
  • Solution: Check user permissions, ensure user can be safely deleted, verify database connectivity

Restore User Failed​

  • Key: users.error.restore.failed
  • Message: "Restoring the user failed. Error: {{error.message}}"
  • Causes:
    • User record is corrupted
    • Insufficient permissions to restore users
    • Database connection issues
  • Solution: Verify permissions, check database status, review user record integrity

Set Team Failed​

  • Key: users.error.set-team.failed
  • Message: "Setting a team for the users failed. Error {{error.message}}"
  • Causes:
    • Target team does not exist
    • Team has been deleted
    • Insufficient permissions
    • Multiple users selected with conflicting team assignments
  • Solution: Verify team exists, check permissions, ensure valid team selection

Failed to Fetch Available Username​

  • Key: users.error.failed-to-fetch-available-username
  • Message: "Failed to fetch an available username. {{error.message}}"
  • Causes:
    • Database query failure
    • Username generation service unavailable
    • Network connectivity issues
  • Solution: Retry operation, check network connection, verify database is accessible

User Name Required​

  • Key: users.error.validation-error.name.required
  • Message: "Name is required"
  • Cause: User name field left empty
  • Solution: Enter a valid user name

Password Doesn't Match​

  • Key: users.error.no-match-error
  • Message: "Password doesn't match"
  • Cause: Password and password confirmation fields don't match
  • Solution: Ensure both password fields contain identical values

đŸ‘Ĩ Teams Page​

File: teams.json

Missing Team​

  • Key: teams.error.missing
  • Message: "Missing team"
  • Cause: Team reference is null or undefined
  • Solution: Ensure team exists before performing operations

Delete Team Failed​

  • Key: teams.error.delete.failed
  • Message: "Deleting the team failed. Error: {{error.message}}"
  • Causes:
    • Team has active users assigned
    • Team is referenced by other entities (projects, registrations)
    • Insufficient permissions
    • Database connection issues
  • Solution: Remove user assignments, check references, verify permissions

Restore Team Failed​

  • Key: teams.error.restore.failed
  • Message: "Restoring the team failed. Error: {{error.message}}"
  • Causes:
    • Team record corrupted
    • Insufficient permissions
    • Database issues
  • Solution: Check permissions, verify database connectivity, review team record

Team Name Required​

  • Key: teams.error.validation-error.name.required
  • Message: "Name is required."
  • Cause: Team name field left empty
  • Solution: Enter a valid team name

📊 Projects Page​

File: projects.json

Delete Project Failed​

  • Key: projects.error.delete.failed
  • Message: "Deleting the project failed. Error: {{error.message}}"
  • Causes:
    • Project has active users working on it
    • Project is in running state
    • Project has associated data (zones, scans, registrations)
    • Insufficient permissions
  • Solution: Close project first, remove dependencies, verify permissions

Restore Project Failed​

  • Key: projects.error.restore.failed
  • Message: "Restoring the project failed. Error: {{error.message}}"
  • Causes:
    • Project record corrupted
    • Insufficient permissions
    • Database connection issues
  • Solution: Verify permissions, check database status

Use Project Failed​

  • Key: projects.error.use.failed
  • Message: "Working on the project failed. Error: {{error.message}}"
  • Causes:
    • Project is not in a valid state (closed, archived)
    • Project is not active
    • User lacks permissions for this project
    • Another user has exclusive access
  • Solution: Verify project state, check permissions, ensure project is active

Search Failed​

  • Key: projects.error.search.failed
  • Message: "Error while searching. Error: {{error.message}}"
  • Causes:
    • Database query timeout
    • Invalid search parameters
    • Network connectivity issues
  • Solution: Simplify search criteria, check network, retry operation

Validation Errors​

  • Key: projects.error.validation-error.*
  • Causes: Invalid project code format, missing required fields
  • Solution: Follow project code format requirements

đŸĸ Branches Page​

File: branches.json

Delete Branch Failed​

  • Key: branches.error.delete.failed
  • Message: "Deleting the branch failed. Error: {{error.message}}"
  • Causes:
    • Branch has active projects
    • Branch has users assigned
    • Insufficient permissions
    • Database connection issues
  • Solution: Remove project assignments, check user assignments, verify permissions

Restore Branch Failed​

  • Key: branches.error.restore.failed
  • Message: "Restoring the branch failed. Error: {{error.message}}"
  • Causes:
    • Branch record corrupted
    • Insufficient permissions
    • Database issues
  • Solution: Check permissions, verify database connectivity

Branch Name Required​

  • Key: branches.error.validation-error.name.required
  • Message: "Name is required"
  • Cause: Branch name field left empty
  • Solution: Enter a valid branch name

đŸĸ Clients Page​

File: clients.json

Delete Client Failed​

  • Key: clients.error.delete.failed
  • Message: "Deleting the client failed. Error: {{error.message}}"
  • Causes:
    • Client has active projects
    • Client has associated branches
    • Insufficient permissions
    • Database connection issues
  • Solution: Remove project/branch dependencies, verify permissions

Restore Client Failed​

  • Key: clients.error.restore.failed
  • Message: "Restoring the client failed. Error: {{error.message}}"
  • Causes:
    • Client record corrupted
    • Insufficient permissions
    • Database issues
  • Solution: Check permissions, verify database connectivity

Validation Errors​

  • Key: clients.error.validation-error.*
  • Causes: Missing required fields, invalid format
  • Solution: Fill all required fields with valid data

🏗ī¸ Zones Page​

File: zones.json

Create Single Zone Failed​

  • Key: zones.form.error.create-single
  • Message: "Could not create the zone "{{zoneCode}}". Error: {{error.message}}"
  • Causes:
    • Zone code already exists
    • Invalid zone code format
    • Project not in valid state
    • Insufficient permissions
    • Database connection issues
  • Solution: Use unique zone code, verify format, check project state and permissions

Create Zone Range Failed​

  • Key: zones.form.error.create-range
  • Message: "Could not create the zone-range. Error: {{error.message}}"
  • Causes:
    • Invalid zone range specification
    • Overlapping zone codes
    • Project not in valid state
    • Insufficient permissions
  • Solution: Verify range parameters, check for conflicts, ensure project is active

Delete Single Zone Failed​

  • Key: zones.form.error.delete-single
  • Message: "Could not delete the zone "{{zoneCode}}". Error: {{error.message}}"
  • Causes:
    • Zone has scans associated
    • Zone has active sessions
    • Zone is in use
    • Insufficient permissions
  • Solution: Close zone sessions, remove scans (if allowed), verify permissions

Delete Zone Range Failed​

  • Key: zones.form.error.delete-range
  • Message: "Could not delete the zone-rang. Error: {{error.message}}"
  • Causes:
    • One or more zones in range have associated data
    • Zones in range are in use
    • Insufficient permissions
  • Solution: Verify each zone can be deleted, close active sessions

No Zone Config​

  • Key: zones.form.error.no-config
  • Message: "No zone code configuration found"
  • Cause: Zone code configuration is missing in settings
  • Solution: Configure zone code settings in system settings

🔍 Zones GoTo Page​

File: zonesgoto.json

Failed to Go to Zone​

  • Key: zonesgoto.error
  • Message: "Failed to go to the zone. Error: {{error.message}}"
  • Causes:
    • Zone does not exist
    • Zone is in invalid state
    • Navigation routing error
    • Insufficient permissions to view zone
  • Solution: Verify zone exists, check permissions, ensure valid zone state

📱 Devices Page​

File: devices.json

Delete Device Failed​

  • Key: devices.error.delete.failed
  • Message: "Deleting the device failed. Error: {{error.message}}"
  • Causes:
    • Device is currently in use
    • Device has active sessions
    • Device has message queue items
    • Insufficient permissions
  • Solution: Ensure device is not in use, clear message queue, verify permissions

Restore Device Failed​

  • Key: devices.error.restore.failed
  • Message: "Restoring the device failed. Error: {{error.message}}"
  • Causes:
    • Device record corrupted
    • Insufficient permissions
    • Database issues
  • Solution: Check permissions, verify database connectivity

Set Device Group Failed​

  • Key: devices.error.set-device-group.failed
  • Message: "Setting the device group for the device failed. Error {{error.message}}"
  • Causes:
    • Target device group does not exist
    • Device group has been deleted
    • Insufficient permissions
  • Solution: Verify device group exists and is active, check permissions

Device Code Required​

  • Key: devices.error.validation-error.code.required
  • Message: "Code is required."
  • Cause: Device code field left empty
  • Solution: Enter a valid device code

Device Name Required​

  • Key: devices.error.validation-error.name.required
  • Message: "Name is required."
  • Cause: Device name field left empty
  • Solution: Enter a valid device name

📱 Device Groups Page​

File: deviceGroups.json

Delete Device Group Failed​

  • Key: deviceGroups.error.delete.failed
  • Message: "Deleting the device-group failed. Error: {{error.message}}"
  • Causes:
    • Device group has devices assigned
    • Device group is referenced by database generation jobs
    • Insufficient permissions
  • Solution: Remove device assignments, check job references, verify permissions

Restore Device Group Failed​

  • Key: deviceGroups.error.restore.failed
  • Message: "Restoring the client failed. Error: {{error.message}}"
  • Note: Error message says "client" but refers to device group
  • Causes:
    • Device group record corrupted
    • Insufficient permissions
    • Database issues
  • Solution: Check permissions, verify database connectivity

Validation Errors​

  • Key: deviceGroups.error.validation-error.*
  • Causes: Missing required fields
  • Solution: Fill all required device group fields

📋 Registrations Page​

File: registrations.json

Delete Registration Failed​

  • Key: registrations.error.delete.failed
  • Message: "Deleting the registration failed. Error: {{error.message}}"
  • Causes:
    • Registration is locked
    • User associated with registration is active
    • Insufficient permissions
    • Database connection issues
  • Solution: Ensure registration can be safely deleted, verify permissions

Restore Registration Failed​

  • Key: registrations.error.restore.failed
  • Message: "Restoring the registration failed. Error: {{error.message}}"
  • Causes:
    • Registration record corrupted
    • User account conflicts
    • Insufficient permissions
  • Solution: Check for user account conflicts, verify permissions

Add Registration Failed​

  • Key: registrations.error.add.failed
  • Message: "Adding the registration failed. Error: {{error.message}}"
  • Causes:
    • Duplicate registration
    • Invalid registration data
    • User already exists
    • Project not accepting new registrations
    • Insufficient permissions
  • Solution: Verify registration uniqueness, check project state, validate data

Temp User Cannot Be Added​

  • Key: registrations.error.add.temp-user
  • Message: "Temp users cannot be added/restored"
  • Cause: Attempting to add or restore a temporary user
  • Solution: Only full-time users can be added through this interface

Change Role Failed​

  • Key: registrations.listing.role.error.failed-saving
  • Message: "Changing the role failed. Error: {{error.message}}"
  • Causes:
    • Invalid role assignment
    • User lacks permission to assign this role
    • Role does not exist
    • Database update failed
  • Solution: Verify role exists, check permission to assign roles, retry operation

Not Allowed to Change Your Own Role​

  • Key: registrations.error.not-allowed-change-yourself
  • Message: "You can't change your own role."
  • Cause: User attempting to modify their own role
  • Solution: Have another administrator change your role

Not Allowed to Demote User​

  • Key: registrations.error.not-allowed-demote
  • Message: "You can't demote another user having more permissions than you."
  • Cause: User attempting to demote a user with higher permissions
  • Solution: Only users with higher permissions can demote this user

Not Allowed to Advance User​

  • Key: registrations.error.not-allowed-advance
  • Message: "You are not allowed to grant more permissions than you have yourself."
  • Cause: User attempting to grant higher permissions than they possess
  • Solution: Only administrators with appropriate permissions can grant this role

📊 Scans Page​

File: scans.json

Save Scan Failed​

  • Key: scans.error.save.failed
  • Message: "An error occurred while trying to update the scan: {{ error.message }}"
  • Causes:
    • Scan is locked by another user
    • Zone session is closed
    • Invalid scan data
    • Scan position already exists
    • Insufficient permissions
  • Solution: Ensure zone session is active, verify scan data, check permissions

Insert Scan Failed​

  • Key: scans.error.insert.failed
  • Message: "An error occurred while trying to add a scan: {{ error.message }}"
  • Causes:
    • Zone session is not in scan mode
    • Duplicate scan position
    • Invalid barcode or position
    • Zone is blocked
    • Insufficient permissions
  • Solution: Verify zone session state, ensure unique position, validate data

Insert Verify Session Failed​

  • Key: scans.error.insert-verify-session.failed
  • Message: "Failed to insert the verify-session: {{ error.message }}"
  • Causes:
    • Zone already has active verify session
    • Zone not in valid state for verification
    • Insufficient permissions
    • Zone has no scans to verify
  • Solution: Close existing sessions, ensure zone has scans, verify permissions

Start Verify Session Failed​

  • Key: scans.error.start-verify-session.failed
  • Message: "Failed to start the verify-session: {{ error.message }}"
  • Causes:
    • Verify session already started
    • Zone session in invalid state
    • Insufficient permissions
  • Solution: Check session state, verify permissions

Abort Verify Session Failed​

  • Key: scans.error.abort-verify-session.failed
  • Message: "Failed to abort the verify-session: {{ error.message }}"
  • Causes:
    • Session already closed
    • Session owned by different user
    • Database update failed
  • Solution: Verify session ownership, check session state

Audit Quota Not Met​

  • Key: scans.error.close-verify-session.audit-quota-failed
  • Message: "You only reached to {{ error.details.scored }} of the required {{ error.details.required }} percent of auditing. Please continue."
  • Cause: User hasn't verified required percentage of scans
  • Solution: Continue verifying scans until quota is met

Verify Not Complete​

  • Key: scans.error.close-verify-session.verify-failed
  • Message: "You haven't audited all the scans, that require audition. Please continue."
  • Cause: Not all scans requiring verification have been verified
  • Solution: Complete verification of all required scans

Close Verify Session Failed​

  • Key: scans.error.close-verify-session.failed
  • Message: "Failed to close the verify-session: {{ error.message }}"
  • Causes:
    • Session in invalid state
    • Required verifications not complete
    • Database update failed
  • Solution: Complete required verifications, retry operation

Approve Scan Failed​

  • Key: scans.error.approve-scan.failed
  • Message: "An error occurred while trying to approve the QM Scan: {{ error.message }}"
  • Causes:
    • Project not in running state
    • Project not active
    • Insufficient permissions (requires team manager or area manager)
    • Scan already approved
  • Solution: Ensure project is running and active, verify permissions

Unapprove Scan Failed​

  • Key: scans.error.unapprove-scan.failed
  • Message: "An error occurred while trying to unapprove the QM Scan: {{ error.message }}"
  • Causes:
    • Project not in running state
    • Project not active
    • Insufficient permissions
    • Scan approved by external system (cannot unapprove)
  • Solution: Ensure project is running, verify permissions, check approval source

📋 Zone Sessions Page​

File: zoneSessions.json

Delete Zone Session Failed​

  • Key: zoneSessions.error.delete.failed
  • Message: "Failed to remove the zone session. Error: {{error.message}}"
  • Causes:
    • Zone session is active
    • Session has associated data
    • Insufficient permissions
  • Solution: Close session first, verify permissions

Restore Zone Session Failed​

  • Key: zoneSessions.error.restore.failed
  • Message: "Failed to restore the zone session. Error: {{error.message}}"
  • Causes:
    • Session record corrupted
    • Zone no longer exists
    • Insufficient permissions
  • Solution: Verify zone exists, check permissions

Unset Busy Flag Failed​

  • Key: zoneSessions.error.unset-busy-flag.failed
  • Message: "Failed to unset the busy flag for the zone session. Error: {{error.message}}"
  • Causes:
    • Session no longer exists
    • Database update failed
    • Concurrent modification conflict
  • Solution: Retry operation, verify session exists

📋 Open Zone Sessions Page​

File: openZoneSessions.json

Abort Session Failed​

  • Key: openZoneSessions.error.abort-session.failed
  • Message: "Failed to abort the session: {{ error.message }}"
  • Causes:
    • Session owned by different user
    • Session already closed
    • Insufficient permissions
  • Solution: Verify session ownership and state

📋 Planning Page​

File: planning.json

Scan Session Failed​

  • Key: planning.error.scan-session.failed
  • Message: "Failed to set the zone to 'Scan - ready'. Reason: {{error.message}}"
  • Causes:
    • Zone already has active session
    • Zone is blocked
    • Zone in invalid state
    • Insufficient permissions
  • Solution: Close existing sessions, unblock zone, verify state

Scan Session Invalid State​

  • Key: planning.error.scan-session.invalid-state
  • Message: "You can't set this zone to 'Scan - ready' while it's on '{{status}}'. It must not be 'Blocked' or in export."
  • Cause: Zone is in a state that doesn't allow scan session creation
  • Solution: Change zone state, unblock zone, or wait for export to complete

Verify Session Failed​

  • Key: planning.error.verify-session.failed
  • Message: "Failed to set the zone to 'Verify - ready'. Reason: {{error.message}}"
  • Causes:
    • Zone has no scans to verify
    • Zone already has verify session
    • Zone is blocked
    • Insufficient permissions
  • Solution: Ensure zone has scans, close existing sessions, unblock zone

Verify Session Invalid State​

  • Key: planning.error.verify-session.invalid-state
  • Message: "You can't set this zone to 'Verify - ready' while it's on '{{status}}'. It must either be 'Scan - ready'or 'Verify - ready'."
  • Cause: Zone is in a state that doesn't allow verify session creation
  • Solution: Change zone to appropriate state first

Block Zone Failed​

  • Key: planning.error.block-zone.failed
  • Message: "Failed to block the zone. Reason: {{error.message}}"
  • Causes:
    • Zone already blocked
    • Zone has active sessions
    • Insufficient permissions
  • Solution: Close active sessions first, verify permissions

Block Zone Invalid State​

  • Key: planning.error.block-zone.invalid-state
  • Message: "You can't set this zone to 'Blocked' while it's on '{{status}}'. It must be 'Undefined'."
  • Cause: Zone must be in undefined state to be blocked
  • Solution: Reset zone to undefined state before blocking

Unblock Zone Failed​

  • Key: planning.error.unblock-zone.failed
  • Message: "Failed to unblock the zone. Reason: {{error.message}}"
  • Causes:
    • Zone not blocked
    • Database update failed
  • Solution: Verify zone state, retry operation

Move Sessions Failed​

  • Key: planning.error.move-sessions.failed
  • Message: "Failed to move the zone-sessions. Reason: {{error.message}}"
  • Causes:
    • Target zone in invalid state
    • Sessions cannot be moved due to state
    • Insufficient permissions
  • Solution: Verify target zone state, check session states

Verify Function Failed​

  • Key: planning.error.verify-function.failed
  • Message: "Failed to evaluate the verify-function. Reason: {{error.message}}"
  • Causes:
    • Invalid verify function configuration
    • Function execution error
    • Missing required data
  • Solution: Check verify function configuration, verify data availability

Initialize Session Failed​

  • Key: planning.error.init-session.failed
  • Message: "Failed to initialize the zone-sessions. Reason: {{error.message}}"
  • Causes:
    • Zone in invalid state
    • Zone already has session
    • Database creation failed
  • Solution: Verify zone state, check for existing sessions

Toggle Flag Failed​

  • Key: planning.error.toggle-flag.failed
  • Message: "Failed to toggle the flag '{{flag}}'. Reason: {{error.message}}"
  • Causes:
    • Invalid flag name
    • Zone in invalid state
    • Database update failed
  • Solution: Verify flag name, check zone state

Transform Scans Failed​

  • Key: planning.error.transform-scans.failed
  • Message: "Failed to run transformScans. Reason: {{error.message}}"
  • Causes:
    • Transformation function error
    • Invalid scan data
    • Configuration issues
  • Solution: Check transformation configuration, verify scan data

Generate PDF Error​

  • Key: planning.sidebar.zone.actions.generate-pdf.error
  • Message: "Generating the pdf failed. Error: {{error.message}}"
  • Causes:
    • PDF generation service unavailable
    • Invalid template
    • Insufficient data for PDF
    • File system permissions
  • Solution: Verify PDF service status, check template, ensure data is complete

Download PDF Failed​

  • Key: planning.sidebar.multi-actions.download.failed
  • Message: "Downloading checklist for zone {{code}} failed"
  • Causes:
    • PDF not generated yet
    • File not found
    • Network issues
    • Permissions issues
  • Solution: Generate PDF first, check file exists, verify permissions

🔄 QM Module Page​

File: qmModule.json

Approve Scan Error​

  • Key: qmModule.error.approve-scan
  • Message: "There was an error approving the scan"
  • Causes:
    • Project not in running state
    • Project not active
    • Insufficient permissions (requires team manager or area manager)
    • Scan already approved
    • Database update failed
  • Solution: Ensure project is running and active, verify permissions

Unapprove Scan Error​

  • Key: qmModule.error.unapprove-scan
  • Message: "There was an error unapproving the scan"
  • Causes:
    • Project not in running state
    • Project not active
    • Insufficient permissions
    • Scan approved by external system (cannot unapprove)
    • No approvedBy field (external approval)
  • Solution: Check project state, verify permissions, check approval source

Approve Zone Error​

  • Key: qmModule.error.approve-zone
  • Message: "There was an error approving the zone"
  • Causes:
    • Project not in running state
    • Project not active
    • Insufficient permissions
    • Zone already approved
  • Solution: Ensure project is running and active, verify permissions

Unapprove Zone Error​

  • Key: qmModule.error.unapprove-zone
  • Message: "There was an error unapproving the zone"
  • Causes:
    • Project not in running state
    • Project not active
    • Insufficient permissions
    • Zone approved by external system
  • Solution: Check project state, verify permissions

Job Failed​

  • Key: qmModule.error.jobfailed
  • Message: "There was an error starting the job"
  • Causes:
    • Job queue unavailable
    • Invalid job configuration
    • Job already running
    • Insufficient system resources
  • Solution: Verify job queue status, check job configuration, retry after current job completes

Load Data Error​

  • Key: qmModule.error.load-data
  • Message: "Could not fetch data. Error:"
  • Causes:
    • Database query timeout
    • Network connectivity issues
    • Insufficient permissions
    • Invalid query parameters
  • Solution: Check network connection, verify permissions, simplify filters

Unknown User​

  • Key: qmModule.error.unknown-user
  • Message: "Unknown"
  • Cause: User who performed action cannot be identified
  • Solution: This is informational - user may have been deleted

📤 Exports Page​

File: exports.json

Start Export Failed​

  • Key: exports.error.start.failed
  • Message: "Starting the export failed. Error: {{error.message}}"
  • Causes:
    • Export already running
    • Insufficient project data
    • Invalid export configuration
    • File system permissions
    • Insufficient disk space
  • Solution: Wait for current export to complete, verify configuration, check disk space

Cancel Export Failed​

  • Key: exports.error.cancel.failed
  • Message: "Canceling the export failed. Error: {{error.message}}"
  • Causes:
    • Export already completed
    • Export not in cancellable state
    • Job queue communication failure
  • Solution: Check export status, verify job state

Remove Export Failed​

  • Key: exports.error.remove.failed
  • Message: "Removing the export failed. Error: {{error.message}}"
  • Causes:
    • Export file in use
    • File system permissions
    • Export job still active
  • Solution: Ensure export is complete or cancelled, check file permissions

Reset Export Sessions Failed​

  • Key: exports.error.reset-export-sessions.failed
  • Message: "Resetting the export sessions failed. Error: {{error.message}}"
  • Causes:
    • Active export sessions
    • Database update failed
    • Insufficient permissions
  • Solution: Cancel active exports first, verify permissions

Update Error​

  • Key: exports.error.update-error
  • Message: "Error fetching update version"
  • Causes:
    • Update service unavailable
    • Network connectivity issues
    • Invalid update configuration
  • Solution: Check network connection, verify update service status

Publish Project Files Error​

  • Key: exports.error.publish-project-files.error
  • Message: "Could not publish project files"
  • Causes:
    • File system permissions
    • Insufficient disk space
    • Network share unavailable
    • Invalid file paths
  • Solution: Check file permissions, verify disk space, ensure network shares are accessible

đŸ“Ĩ Imports Page​

File: imports.json

Import Failed​

  • Key: imports.error.import.failed
  • Message: "Import failed. Error: {{error}}"
  • Causes:
    • Invalid file format
    • File doesn't match filename regex pattern
    • File type not allowed for this import
    • File linked to active job
    • Parsing errors in file content
    • Validation failures
    • Database insertion errors
  • Solution: Verify file format, check filename pattern, ensure file type is allowed, validate file content

Filename Invalid​

  • Key: imports.error.filename.invalid
  • Message: "Filename does not match regular expression: {{ exp }}"
  • Cause: Uploaded file name doesn't match the required pattern
  • Solution: Rename file to match the required pattern shown in the error

File Type Invalid​

  • Key: imports.error.filetype.invalid
  • Message: "File type is not allowed"
  • Cause: File extension or MIME type not allowed for this import type
  • Solution: Convert file to an accepted format

Update Error​

  • Key: imports.error.update-error
  • Message: "Error fetching update version"
  • Causes:
    • Update service unavailable
    • Network connectivity issues
  • Solution: Check network connection, retry operation

Template Failed​

  • Key: imports.error.template.failed
  • Message: "Failed to generate registrations template"
  • Causes:
    • Template generation service error
    • Missing template configuration
    • File system permissions
  • Solution: Verify template configuration, check file permissions

💾 Database Page​

File: database.json

Start Database Generation Failed​

  • Key: database.error.start.failed
  • Message: "Starting the generation of the database failed. Error: {{error.message}}"
  • Causes:
    • Database generation already running
    • Insufficient project data
    • Invalid configuration
    • Device group not found
    • File system permissions
  • Solution: Wait for current generation, verify configuration, check device groups

Cancel Database Generation Failed​

  • Key: database.error.cancel.failed
  • Message: "Canceling the generation of the database failed. Error: {{error.message}}"
  • Causes:
    • Job already completed
    • Job not in cancellable state
    • Job queue communication failure
  • Solution: Check job status, verify job state

Remove Database Failed​

  • Key: database.error.remove.failed
  • Message: "Removing the generation of the database failed. Error: {{error.message}}"
  • Causes:
    • Database file in use
    • File system permissions
    • Job still active
  • Solution: Cancel job first, check file permissions

Upload Database Failed​

  • Key: database.error.upload.failed
  • Message: "Upload database failed. Error: {{error.message}}"
  • Causes:
    • Invalid database file format
    • File too large
    • Network timeout
    • File system permissions
    • Database validation failed
  • Solution: Verify file format, check file size, ensure network stability

Insert Device Message Failed​

  • Key: database.error.insert-message.failed
  • Message: "Sending a message to a device failed. Error: {{error.message}}"
  • Causes:
    • Device not found
    • Device offline
    • Invalid message format
    • Message queue full
  • Solution: Verify device exists and is online, check message format

Insert Device Group Message Failed​

  • Key: database.error.insert-message-group.failed
  • Message: "Sending a message to a device-group failed. Error: {{error.message}}"
  • Causes:
    • Device group not found
    • No devices in group
    • Invalid message format
  • Solution: Verify device group exists and has devices, check message format

Remove Device Message Failed​

  • Key: database.error.remove-message.failed
  • Message: "Removing a message for a device failed. Error: {{error.message}}"
  • Causes:
    • Message already processed
    • Device not found
    • Database update failed
  • Solution: Verify message and device exist, retry operation

Remove Device Group Message Failed​

  • Key: database.error.remove-message-group.failed
  • Message: "Removing a message for a device-group failed. Error: {{error.message}}"
  • Causes:
    • Messages already processed
    • Device group not found
    • Database update failed
  • Solution: Verify device group exists, retry operation

📊 Dashboard Page​

File: dashboard.json

QR Code Generation Error​

  • Key: dashboard.charts.popover.qrError
  • Message: "There was an error generating the QR Code"
  • Causes:
    • QR code generation library failure
    • Invalid data for QR encoding
    • Data too large for QR code
  • Solution: Verify data is valid and not too large, retry generation

Insert Chart Failed​

  • Key: dashboard.error.insert.failed
  • Message: "Adding a chart failed. Error: {{error.message}}"
  • Causes:
    • Invalid chart configuration
    • Insufficient permissions
    • Database insert failed
    • Maximum charts limit reached
  • Solution: Verify chart configuration, check permissions, verify chart limits

Edit Chart Failed​

  • Key: dashboard.error.edit.failed
  • Message: "Updating a chart failed. Error: {{error.message}}"
  • Causes:
    • Chart not found
    • Invalid chart configuration
    • Insufficient permissions
    • Concurrent modification conflict
  • Solution: Verify chart exists, validate configuration, check permissions

Remove Chart Failed​

  • Key: dashboard.error.remove.failed
  • Message: "Removing a chart failed. Error: {{error.message}}"
  • Causes:
    • Chart not found
    • Insufficient permissions
    • Database delete failed
  • Solution: Verify chart exists, check permissions

User Preferences Update Failed​

  • Key: dashboard.error.user-preferences-upsert-failed
  • Message: "Update user preferences failed. Error: {{error.message}}"
  • Causes:
    • Invalid preferences data
    • Database update failed
    • Concurrent modification
  • Solution: Verify preferences data format, retry operation

🔔 Notifications Page​

File: notifications.json

Resolve Notification Failed​

  • Key: notifications.error.resolve-failed
  • Message: "Error resolving notification: {{error}}"
  • Causes:
    • Notification not found
    • Notification already resolved
    • Insufficient permissions
    • Database update failed
  • Solution: Verify notification exists and is unresolved, check permissions

Assign Notification Failed​

  • Key: notifications.error.assigned-failed
  • Message: "Error assigning notification: {{error}}"
  • Causes:
    • Notification not found
    • Invalid user assignment
    • Notification already assigned
    • Insufficient permissions
  • Solution: Verify notification exists, validate user, check permissions

🚀 Navigation (Project Lifecycle)​

File: navigation.json

General Navigation Error​

  • Key: navigation.error.general
  • Message: "An error occurred while trying to [open/close/restore] the project: {{ error.message }}"
  • Causes:
    • Project not found
    • Project in invalid state
    • Insufficient permissions
    • Database connection issues
  • Solution: Verify project exists, check project state, verify permissions

Zone Quota Not Met​

  • Key: navigation.error.zone-quota-not-met
  • Message: "This project can't be closed now. The Quota of audited zones of {{ error.details.zoneQuota }} is not met. {{ error.details.verifiedZonesNeeded - error.details.verifiedZones }} Zone(s) is/are missing."
  • Cause: Required percentage of zones have not been audited
  • Solution: Audit additional zones to meet the required quota percentage

Zone Verified Quota Not Met​

  • Key: navigation.error.zone-verified-quota-not-met
  • Message: "This project can't be closed now. The zone verification quota hasn't been reached: you have verified {{ error.details.verifiedZones }} out of {{ error.details.verifiedZonesNeeded }} Zone(s) but you need to verify {{ error.details.verifiedZonesNeeded - error.details.verifiedZones }} more Zone(s)."
  • Cause: Insufficient zones have been verified to meet project closure requirements
  • Solution: Verify the required number of additional zones before closing

Quality Assurance Quota Not Met​

  • Key: navigation.error.quality-assurance-quota-quota-not-met
  • Message: "This project can't be closed now. An internal auditor needs to verify {{ error.details.verifiedZonesNeeded - error.details.verifiedZones }} additional zones to meet his quota of {{ error.details.qamQuota }}%."
  • Cause: Quality assurance manager hasn't met their verification quota
  • Solution: QAM must verify additional zones to meet their required percentage

Same Scan Verify User​

  • Key: navigation.error.same-scan-verify-user
  • Message: "This project can't be closed now. In the zone "{{ error.details.zone.code }}" a user scanned and verified."
  • Cause: Same user both scanned and verified a zone (violates audit independence)
  • Solution: Have a different user verify the zone

Zones Need Verification​

  • Key: navigation.error.verify-failed
  • Message: "This project can't be closed now. The zones "{{ error.details.zones }}" need verification."
  • Cause: Specified zones require verification before project can be closed
  • Solution: Verify all listed zones

Zones Need Verification + QM Notifications​

  • Key: navigation.error.verify-failed-and-qm-notifications
  • Message: "This project can't be closed now. The zones "{{ error.details.zones }}" need verification.|There are pending items awaiting approval in the QM Module."
  • Causes:
    • Zones need verification
    • QM module has unapproved items
  • Solution: Verify zones and approve pending QM notifications

Unverified Empty Zones with Rescan​

  • Key: navigation.error.unverified-empty-zones-with-rescan
  • Message: "This project can't be closed now. The zones "{{ error.details.unverifiedTriggeredZones }}" need verification."
  • Cause: Empty zones with rescan triggers require verification
  • Solution: Verify the specified zones that were triggered for rescan

Deviant Zone Verification​

  • Key: navigation.error.deviant-zone-verification-verifications-needed
  • Message: "This project can't be closed now. The zones "{{error.details.zones}}" have a deviant zone verification"
  • Cause: Zones have deviant verification status requiring resolution
  • Solution: Review and resolve deviant zone verifications

Project Reopen Error​

  • Key: navigation.error.project-reopen-error
  • Message: "This project can't be reopened. Configuration settings prevent the project from reopening."
  • Cause: ReopenProject setting is set to "do_not_allow" or "allow_closed" and project is in wrong state
  • Solution: Check project settings configuration, verify project can be reopened

Project Publish Error​

  • Key: navigation.error.project-publish-error
  • Message: "This project can't be published. The project must close first."
  • Cause: Attempting to publish a project that is not in closed state
  • Solution: Close the project before attempting to publish

Update Archived Project Error​

  • Key: navigation.error.update-archived-project-error
  • Message: "This project can only change status after it is restored."
  • Cause: Attempting to change status of archived project without restoring first
  • Solution: Restore the project before changing its status

ℹī¸ Introduction Page​

File: introduction.json

Introduction Error​

  • Key: introduction.error.error
  • Message: "Error: {{error.message}}"
  • Causes:
    • Invalid introduction content
    • Template rendering failure
    • Database query failed
    • File upload error
  • Solution: Check introduction content format, verify database connectivity

⚙ī¸ Settings Page​

File: settings.json

Update Setting Failed​

  • Key: settings.error.update-setting.failed
  • Message: "Failed to update the setting. Reason: {{error.message}}"
  • Causes:
    • Invalid setting value
    • JSON parsing error
    • Insufficient permissions
    • Database update failed
  • Solution: Verify setting value format, check JSON syntax, verify permissions

📋 Main Application Errors​

File: main.json

Project Not Active​

  • Key: main.error.project-not-active
  • Message: "The project is not active"
  • Cause: Attempting to work on a project that has been deactivated
  • Solution: Contact administrator to activate the project

No Current Project​

  • Key: main.error.no-current-project
  • Message: "You have to choose a project first"
  • Cause: Attempting to access project-specific functionality without selecting a project
  • Solution: Select a project from the dashboard first

Access Denied​

  • Key: main.error.access-denied
  • Message: "Access denied"
  • Cause: User lacks permissions to access the requested resource
  • Solution: Contact administrator to request appropriate permissions

Setting Load Error​

  • Key: main.error.settings.load
  • Message: "Could not load the setting "{{setting}}". Error: {{error.message}}"
  • Causes:
    • Setting not found
    • Database query failed
    • Permission denied
  • Solution: Verify setting exists, check database connection, verify permissions

Extra Zone Flags Parse Error​

  • Key: main.error.settings.ExtraZoneFlags.parse
  • Message: "The setting "Extra zone flags" contains an invalid JSON string. Error: {{error.message}}"
  • Cause: ExtraZoneFlags setting contains malformed JSON
  • Solution: Correct JSON syntax in ExtraZoneFlags setting

Scan Flow Config Parse Error​

  • Key: main.error.settings.ScanFlowConfig.parse
  • Message: "The setting "Scan Flow Config" is not valid. Error: {{error.message}}"
  • Cause: ScanFlowConfig setting has invalid structure or values
  • Solution: Verify ScanFlowConfig format against requirements

Verify Reasons Parse Error​

  • Key: main.error.settings.VerifyReasons.parse
  • Message: "The setting "Verify reasons" is not valid. Error: {{error.message}}"
  • Cause: VerifyReasons setting has invalid format
  • Solution: Correct VerifyReasons setting structure

File Remove Failed​

  • Key: main.file.error.remove.failed
  • Message: "Removing the file failed. Reason: {{error.message}}"
  • Causes:
    • File is linked to an active job
    • File system permissions
    • File in use
    • File not found
  • Solution: Cancel associated job first, check file permissions, verify file exists

Job Remove Failed​

  • Key: main.job.error.remove.failed
  • Message: "Removing the job failed. Reason: {{error.message}}"
  • Causes:
    • Job is still running
    • Job not found
    • Database delete failed
  • Solution: Cancel job first if running, verify job exists

Job Cancel Failed​

  • Key: main.job.error.cancel.failed
  • Message: "Canceling the job failed. Reason: {{error.message}}"
  • Causes:
    • Job already completed
    • Job not in cancellable state
    • Job queue communication failure
  • Solution: Check job status, verify job can be cancelled

✅ Form Validation Errors​

File: formValidation.json

Field Required​

  • Key: formValidation.required
  • Message: "This field is required"
  • Cause: Required form field left empty
  • Solution: Fill in the required field

Pattern Mismatch​

  • Key: formValidation.pattern
  • Message: "The value does not match the required pattern"
  • Cause: Field value doesn't match expected format (e.g., email, phone number)
  • Solution: Enter value in correct format

Minimum Value​

  • Key: formValidation.min
  • Message: "Minimum value is {{value}}"
  • Cause: Numeric field value is below minimum allowed
  • Solution: Enter value greater than or equal to minimum

Maximum Value​

  • Key: formValidation.max
  • Message: "Maximum value is {{value}}"
  • Cause: Numeric field value exceeds maximum allowed
  • Solution: Enter value less than or equal to maximum

Maximum Length​

  • Key: formValidation.maxlength
  • Message: "Maximum length is {{value}}"
  • Cause: Text field exceeds maximum character length
  • Solution: Shorten text to meet maximum length requirement

📊 Error Summary by Category​

🔐 Permission & Access Errors​

  • Insufficient permissions for CRUD operations
  • Access denied to resources
  • Role-based restrictions
  • Cannot modify own permissions

📋 Data Validation Errors​

  • Required fields missing
  • Invalid formats (JSON, patterns, lengths)
  • Duplicate values
  • Data integrity violations

🔄 State & Workflow Errors​

  • Invalid project states (not running, not active, archived)
  • Invalid zone states (blocked, in export, wrong mode)
  • Session state conflicts
  • Audit quotas not met
  • Verification requirements not met

🗄ī¸ Database & System Errors​

  • Connection failures
  • Query timeouts
  • Concurrent modifications
  • Record not found
  • Update/delete failures

📁 File & Job Errors​

  • File in use
  • Invalid file format/type
  • Filename pattern mismatch
  • Job already running
  • Job queue failures
  • Disk space issues

🔗 Dependency & Reference Errors​

  • Entity has dependent records
  • Referenced entity not found
  • Cannot delete due to associations
  • Device/group not found

🆘 General Troubleshooting Guidelines​

1. Check User Permissions​

  • Verify user has appropriate role (Admin, Team Manager, Area Manager, Employee, Observer, QA Manager, External Auditor)
  • Confirm project-level registration and role
  • Check system-level permissions for administrative operations

2. Verify Project State​

  • Ensure project is "running" for most operations
  • Confirm project is "active" (isActive = true)
  • Check if operation requires "closed" or specific state
  • Review project lifecycle restrictions

3. Check Active Sessions & Jobs​

  • Close blocking zone sessions
  • Wait for running jobs to complete or cancel them
  • Verify no concurrent operations on same resource
  • Check job queue status

4. Validate Input Data​

  • Fill all required fields
  • Match expected formats (JSON, regex, dates)
  • Verify data uniqueness where required
  • Check data type and range constraints

5. Review Dependencies​

  • Check for child records preventing deletion
  • Verify referenced entities exist
  • Ensure no circular dependencies
  • Clear blocking associations first

6. Check System Resources​

  • Verify database connectivity
  • Check network connection
  • Confirm sufficient disk space
  • Verify file system permissions

7. Retry & Escalate​

  • Retry transient errors
  • Clear browser cache if UI issues
  • Check browser console for client errors
  • Review server logs for detailed errors
  • Contact system administrator for persistent issues

📝 Notes​

  • Error Message Format: Most errors follow the pattern: "[Action] failed. Error: \{\{error.message\}\}" where \{\{error.message\}\} contains the specific technical error
  • Translation Variables: Variables in \{\{ \}\} are replaced at runtime with actual values
  • Pluralization: Some messages use .mf (MessageFormat) for proper singular/plural handling
  • Nested Errors: error.details.* properties contain additional context like counts, codes, percentages
  • State Validation: Many errors include current state in the message to help users understand why the operation failed
  • Permissions Model: Operations are restricted by role hierarchy: System Admin > Area Manager > Team Manager > QA Manager > Employee > Observer > External Auditor

This reference is generated from translation files dated November 7, 2025. For the most current error messages, refer to the ui/components/stripes/translations/en/ directory.