What happens on expiry?
Held jobs have a timeout and an automatic expiry setting. Cleaning the queue instead of printing uncollected documents reduces unnecessary buildup. This is separate from archive retention and has a different data lifecycle.
Configuration
- Open the held job settings under Settings in the management console.
- Set a timeout in hours that fits your organization’s working pattern.
- Check whether automatic expiry is enabled.
- Submit a test job without releasing it and inspect its state after the timeout.
- Tell users that an expired document may need to be submitted again.
Choosing a timeout
A short timeout can affect users who reach a device after a meeting or shift change. A long timeout increases queue size. Measure pilot usage first and choose according to your policy.
Unexpected removal
Confirm that the job expired rather than being deleted or released earlier. Check the server clock and time zone. A default value in source code is not necessarily the value configured for your organization.
