Print jobs queued through the same printer/queue aren't processing in the order their Job IDs were created — what actually controls the processing order, and is there a way to force strict Job-ID sequence?

All FAQ questions / Reporting and analytics

Answer

The processing order (and whether errors halt the queue) is controlled by the EXECUTION_MODE and THREAD_COUNT settings on the relevant batch queue, configured under Solution Manager > Integration > IFS Connect > Setup IFS Connect. Setting EXECUTION_MODE to 'InSequence' with THREAD_COUNT set to 1 processes jobs strictly in Job ID order. Note the related 'InOrder' mode behaves differently — with that mode, if one job in the sequence errors, processing of all subsequent jobs in that queue stops rather than continuing past the failed one, which is an important behavioral difference to account for when choosing between the two.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Reporting and analytics questions