Troubleshooting
- Last UpdatedMar 17, 2026
- 1 minute read
Common issues that can occur when validating data.
403 Forbidden on create/update operations
Cause: Your role doesn't include the required action. Data Viewer and Account Member are read-only.
Fix: Ask your account administrator to assign a role with write permissions (Data Writer, Data Manager, or higher).
Upload returns 400 Bad Request
Common causes:
-
File format not supported (use CSV, Excel .xlsx, JSON, or NDJSON)
-
CSV separator character doesn't match the file's actual delimiter
-
Excel file is corrupted or password-protected
-
ClassLibrary file is not a valid Information Standards definition
Etag mismatch on update/delete
Cause: Another user or process modified the entity since your last read.
Fix: Re-read the entity to get the latest etag, then retry.
Session stuck in IN_PROGRESS
Check: Large datasets take time. Monitor numberOfObjectsValidated vs numberOfObjectsToValidate. If progress stalls, check application health via the health endpoint.
Export file expired
Cause: Exports default to 1-hour retention. If you're past that window, re-trigger the export.
Prevention: Set retentionPeriodInMinutes to a longer value when creating the export, or download immediately after completion.
Consistency check shows dataset incompatible with class library
Cause: The dataset columns don't map to the class library vocabulary.
Check: Inspect the file section properties and compare against the class library's file mappings. Use ignoreUnmappedColumns: true during upload if unrecognized columns are expected.
No issues found but data quality is poor
Check: Verify the correct class library and vocabulary are selected. Different vocabularies apply different rule sets. Also check if rule severities have been overridden to lower levels.