MICROEXTRACT DOCUMENTATION

MicroExtract Troubleshooting and FAQ

Start with the visible status and exact error message. Avoid changing multiple settings at once because that makes the root cause harder to identify.

1. A source document will not upload

Confirm that the file is a supported PDF, the file is within the plan and application limits, and the browser session is still valid. Try a known-good representative PDF before changing the template.

2. A template will not validate

Confirm that the selected output format matches the uploaded template file type and that the approved profile is correct. Template validation errors usually indicate that a required structural element is missing or the file is not the expected format.

3. A job is still processing

Use Live Status and allow automatic reconnect to recover from temporary status interruptions. Do not resubmit the same source repeatedly unless the current job is known to have failed or expired.

4. A field is missing or low confidence

Compare the field with the source document. Check whether the value is actually present, readable and labelled consistently. If the same variation repeats, propose an approved alias or rule instead of making a one-off manual assumption.

5. The job says review required

Read the listed validation reasons and inspect the source. A review state means the workflow intentionally stopped short of treating the output as fully trusted.

6. A selected output is not available

Confirm that the format was selected and its template was validated before processing. Customer outputs are finalized after processing reaches an accepted terminal state, so there can be a short interval between extraction completion and all download files becoming available.

7. Use the MicroExtract Assistant for product guidance

The in-product assistant is intended for read-only help such as template guidance, confidence explanations, output questions and troubleshooting. It should not silently change customer records, templates or security settings.

Need help with a real document workflow?

Use representative samples, define the required output and validation rules, then test before production use.

Troubleshooting Without Duplicate Processing

When a workflow does not finish as expected, identify its current state before retrying. Keep the source and job reference available without exposing confidential document contents.

Choose the right next check

SymptomSafe first checkAvoid
Cannot uploadWorkspace access, permitted type and current file limitDisabling security or using another tenant
No templateApproved mapping and validated revisionGuessing a schema from a competitor example
Job still processingExisting job status and referenceRepeated submission without checking
Review requiredVisible reasons and original sourceTreating review as silent success
Missing export formatAccount entitlement and selected templateAssuming every plan permits every format
Email not receivedWhether delivery is actually enabled and requestedClaiming provider acceptance proves inbox receipt

Prepare a useful support request

Provide the non-sensitive job reference, approximate time, visible error code, browser and expected action. Use the approved support channel for any further evidence.

Do not place API keys, authentication tokens, full documents or personal records in public comments or analytics payloads.

Keep the original evidence

If a retry is authorised, record whether it is a retry of an existing attempt or a genuinely new processing request. Retain any relevant review state.

Changes to a mapping or output template should be tested on representative examples before returning to routine use.