Troubleshooting guidance
Resolve import errors
Use validation and row outcomes to correct a source file without creating partial uncertainty.
- FOR
- Organisation administrator, Procurement, Finance
- OUTCOME
- Use RAQOZ to use validation and row outcomes to correct a source file without creating partial uncertainty.
Before you begin
- The affected organisation, record and user are known.
- You can describe the expected and actual state without sharing credentials.
Guidance
- 1
Review required-field, format and mapping errors in the validation preview.
- 2
Confirm duplicate handling matches the intended create, skip or update behavior.
- 3
Correct the source file or mapping and validate again.
- 4
Review the recorded row outcomes after import.
Evidence RAQOZ retains
- Validation errors
- Mapping and duplicate choice
- Row-level import outcome
Common issues
The problem continues after these checks.
Record the organisation, affected record ID, expected state, actual state and time, then contact support without sending passwords, one-time codes, bank credentials or confidential documents.
A workaround would bypass the control.
Do not use the workaround. Keep the blocked or exceptional state visible and escalate through the accountable product or support path.
Related articles
Last reviewed 2 September 2026. Review against the current production release before relying on exact screen behavior.