Limits and retention
Resource limits apply to isolated scanner/processor operations. Defaults are used when the policy's limits object is absent or null. An operation exceeding its budget is stopped or held; a higher value does not prove the endpoint can handle the workload.
Resource limits
| Option | Default | Accepted values | Behavior |
|---|---|---|---|
maxInputBytes |
268435456 | Positive integer bytes | 256 MiB total acquired input/master budget |
maxPages |
500 | Positive integer | Maximum pages per batch/document |
maxPagePixels |
100000000 | Positive integer pixels | Per-page decoded pixel ceiling |
maxWorkerBytes |
2147483648 | Integer >= 134217728 bytes | 2 GiB default worker memory limit; minimum 128 MiB |
timeoutSeconds |
600 | Positive integer seconds | Worker lifetime budget, default ten minutes |
Paperweight currently holds a batch in memory inside the isolated worker. Test a batch as large as your team expects to handle, checking available RAM, disk space, and processing time. Lower resolution can reduce resource use but is a lossy policy decision requiring document review.
Retention is fixed in this version
archiveDays must be 7 and historyDays must be 90. These JSON fields describe fixed supported policies; other values are rejected. They are not user-selectable retention durations in this release.
Successful jobs become eligible for archive expiration seven days after publication once cleanup has completed and their recorded state is Archived. Cleanup runs while the application is running; seven days is an eligibility boundary, not an exact deletion-time service guarantee.
Warning
Archive expiration permanently deletes eligible local originals and job artifacts. Paperweight cannot recover these deleted files. Confirm that this retention period meets your needs before enabling live workflows.
Failed, incomplete, uncertain, and unexpected-content archives remain held for review. Linked directories, unexpected subdirectories, and unexpected artifacts prevent ordinary expiration. Investigate the reason instead of manually bypassing protection.
Activity events older than ninety days are removed. Records for expired jobs are removed when they have not been updated for ninety days. Unresolved job records remain available for review beyond that period.
Storage planning
Local storage needs include original masters, output, temporary processing files, and retained archives. Final document compression savings do not represent peak working-space savings. Account for incomplete and held work, which does not expire automatically, and monitor available disk space during normal use.
Uninstall preserves policy, local job stores, and archives. It is not a retention or cleanup operation. Establish a separate authorized process for any eventual data disposal.