Table of Contents

Troubleshooting

Find your error code or symptom below to choose the next step. Check the document and configuration before changing processing settings; allowing more transformations can change the resulting document.

Symptom or code Check and next action
Inactive / no workflow Valid managed policy, enabled source, ownerMachine and ownerUser matching the interactive session
ConfigurationRejected Unknown properties, required arrays/IDs, invalid profile settings, overlapping roots; validate a corrected policy before deployment
UnsupportedPolicyVersion Configuration schema must be 1, archiveDays 7, historyDays 90, revision >= 1
SourceOwnerRequired Enabled source needs both workstation and Windows account ownership
OverlappingRoots Separate source, destination, staging, and data-root directory trees
ProtectedStorageConfirmationRequired Clinical mode is enabled without storage confirmation. Ask your administrator to review storage protection, then record the result with protectedStorageConfirmed: true. See Clinical mode.
ProfileNotQualified At least one profile has validatedForClinicalUse: false while clinical mode is enabled. Ask your administrator to confirm the profile's document quality and record the result. See Clinical mode.
No scanners / ScannerUnavailable Vendor driver installation, device connection, current-user access, and selected provider
ScannerCapabilityNotReported The driver has not reported the required settings. Use the scanner's settings dialog and test a sample scan.
FeederEmpty / PaperJam / ScannerDisconnected Review retained pages, recover the physical condition, and confirm completeness before finishing
LocalStorageRequired / SynchronizedStorageRejected Move planned spool to protected fixed local storage using an authorized recovery procedure
AccessDenied / FileIoFailure Actual operator permissions, locks, disk space, path availability, and endpoint controls
DestinationUnavailable Final folder exists and is reachable by the operator
DestinationCollision / StagingCollision Investigate existing file identity and delivery history; do not overwrite blindly
PublicationUncertain / ReconcileWithInteleFiler Confirm delivery with the receiving system before resubmitting; either code can appear with any destination
PublicationReviewRequired A publication intent blocks retry to avoid duplicate delivery
ResumeCaptureRequired Resume an incomplete scanner batch rather than retrying it as a completed document
SourceChangedResubmit Original folder file identity/content changed; arrange a deliberate new submission

Content or profile holds

Encrypted and active PDFs are held. Signature-bearing PDFs require eligible unchanged passthrough. Metadata or complex-PDF transformations can be held when the requested policy cannot be safely established. Codec restrictions do not make an unsupported encoder available.

Page, input-byte, pixel, output-size, or resolution errors require comparison with the approved profile and the actual document. Resource errors may indicate an oversized batch or endpoint capacity problem. If you split a batch or scan it again, follow your team's recovery steps and check that every page is included in the correct order.

For an unsupported file, keep the original intact. If possible, provide support with a small sample that contains no patient information and explain the result you expected.

Maintenance remains active

If Paperweight exits or stays stopped after a failed administrative session, check for the protected maintenance.flag file and the installer log. Establish that no installation is active before correcting a stale marker through an administrator. Do not kill processing workers to make an upgrade proceed.

Support context

Provide product version, documentation revision, policy/profile revision, acquisition type, error code, and whether delivery is confirmed or uncertain. Describe the scanner/provider or target contract without transmitting patient information. Clinimatix contact: hello@clinimatix.com.