Operations and recovery
Assign responsibility for held jobs, source health, storage capacity, and downstream reconciliation before enabling unattended intake. The app operates in the signed-in user's session and has no central fleet monitoring service.
Daily checks
Review Activity for Held, Uncertain, or persistently Published jobs and inspect source health. Confirm documents appear in the receiving application's actual workflow. Watch working-space growth, especially incomplete/held archives that do not expire automatically.
Keep Paperweight's local data on a protected fixed disk on the workstation. Network shares and synchronized folders are not suitable for the local job store.
Restart recovery
| Interrupted state | Recovery behavior |
|---|---|
| Processing | Returns to Queued for another processing attempt |
| Acquiring | Held for incomplete acquisition/capture review |
| Publishing | Compare recorded final path/hash; ambiguous or missing output becomes Uncertain |
| Validated | Retained result can proceed to publication |
| Published | Source cleanup/archive can continue |
An expected final file with the recorded hash can confirm publication after interruption. Its absence cannot prove that publication failed: the consumer may have already ingested and removed it.
Held documents
Select a held job in Activity and investigate its error. Retry held document applies only to eligible Held jobs. It is blocked if a publication intent exists, preventing blind redelivery. Incomplete scanner capture uses Resume incomplete capture instead.
An interrupted folder acquisition can retry only while the source still has its recorded identity and hash. If it changed, arrange a deliberate new submission rather than editing recovery metadata.
Uncertain publication
Warning
Do not blindly retry, copy the document into intake again, delete publication metadata, or restore an old queue. Reconcile with the downstream operator first; duplicate clinical documents can result.
Compare the protected recorded publication intent and the receiving system's intake evidence under an authorized support process. The application has no automatic EHR-accepted status and no general-purpose UI command that safely resolves every uncertain publication.
Protected material and support
Original content, job snapshots, source paths, scanner preferences, and processing artifacts remain local. ACLs allow the current user, SYSTEM, and Administrators. This does not itself establish disk encryption, compliant backups, or safe crash dumps.
When requesting help, use sample documents without patient information whenever possible. Share only the approved diagnostic details needed for support, such as your product/configuration revision and error code. Keep patient documents, source paths, account secrets, and raw job data out of public tools. The installer log is %ProgramData%\Clinimatix\Paperweight\installer.log; handle it according to your organization's information-sharing policy.
See Limits and retention for archive deletion schedules and Rollout for maintenance and rollback guidance.