Errors & Troubleshooting
This page maps common runtime errors to practical recovery actions.
Access denied
Meaning: your role or environment policy does not allow the action.
What to do:
- Re-check role scope in Settings
- Ask Owner to verify access policy
- Retry after re-login if role was changed
Storage / folder not accessible
Meaning: bound source folder is not reachable.
What to do:
- Reconnect source
- Reselect folder binding
- Confirm account/session is correct
Upload failed
Meaning: source file cannot be ingested/parsing cannot start.
What to do:
- Validate file readability
- Retry with cleaner source
- Check connector/folder state
Processing incomplete
Meaning: parser returned partial extraction.
What to do:
- Reparse via canonical or ZenoLab route
- Correct fields manually
- Use Accuracy Review checklist for systematic mismatches
VAT unknown or not determined
Meaning: VAT status could not be finalized in current run.
What to do:
- Verify VAT manually from source
- Retry validation later
- Continue according to your compliance process
Documents locked
Meaning: document is currently non-editable by lifecycle/policy.
What to do:
- Verify document status
- Confirm role/subscription scope
- Escalate through support if lock is unexpected
Wallet service not available (501)
Meaning: wallet backend is offline or not implemented for this environment.
What to do:
- Use demo provider mode if enabled
- Continue pilot with document flows
- Request environment rollout for wallet connector service
Audit restricted (403)
Meaning: your role is outside audit visibility scope.
What to do:
- Ask Owner to assign
admin/auditorif needed - Use compliance-export process available to your role
Source link unavailable
Meaning: browser could not resolve/open original source reference.
What to do:
- Rebind local folder / connector
- Use Change folder for local mode
- In Safari, use reconnect flow (direct local path opening is restricted)