Skip to main content

Errors & troubleshooting

This page maps the runtime errors you are most likely to see during a pilot session to practical recovery steps. If your case is not here, write to me directly.

Access denied​

What it means: your role or the current environment policy does not allow the action.

What to do:

  1. Re-check your role scope in Settings.
  2. Ask the Owner to verify the access policy.
  3. Retry after re-login if your role was just changed — the new scope only takes effect on the next session.

Storage / folder not accessible​

What it means: the bound source folder is no longer reachable.

What to do:

  1. Reconnect the source via Change folder.
  2. Reselect the folder binding.
  3. Confirm the account and session you are signed into are the right ones.

Upload failed​

What it means: the source file cannot be ingested, or parsing cannot start.

What to do:

  1. Verify the file is readable and in a supported format.
  2. Retry with a cleaner source.
  3. Check the connector or folder state.

Processing incomplete​

What it means: the parser returned only partial extraction.

What to do:

  1. Reparse via Canonical Route or ZenoLab.
  2. Correct missing or wrong fields manually in the preview.
  3. Use the Accuracy Review checklist for mismatches you want the system to learn from.

VAT unknown or not determined​

What it means: the VAT validation could not be finalised in the current run.

What to do:

  1. Verify the VAT manually against the source document.
  2. Retry validation later — service availability fluctuates.
  3. Continue the review based on your own compliance process. A non-final VAT status is not a hard block.

Documents locked​

What it means: the document is currently non-editable because of lifecycle or policy rules.

What to do:

  1. Verify the document's current status.
  2. Confirm your role and subscription scope cover the edit.
  3. If the lock is unexpected, reach out directly.

Wallet service not available (501)​

What it means: the wallet backend is offline or not implemented for this environment.

What to do:

  1. Switch to demo provider mode if it is enabled.
  2. Continue the pilot with document flows — wallets are optional.
  3. Request a wallet-connector rollout for your environment when it becomes necessary.

Audit restricted (403)​

What it means: your role is outside the audit visibility scope.

What to do:

  1. Ask the Owner to assign admin or auditor if you need that level of access.
  2. Use the compliance-export process available to your current role in the meantime.

What it means: the browser could not resolve or open the original source reference.

What to do:

  1. Rebind the local folder or the connector.
  2. Use Change folder to reconnect local-folder context.
  3. In Safari, use the reconnect flow — Safari restricts direct opening of local folder paths from a web UI.

When none of the above fit​