Normally, when a transaction is placed on a queue, it is eligible for execution as soon as the Queued Transaction Scheduler is able to find an idle Arbortext PE sub-process in a Arbortext PE sub-process pool that can accept the transaction. However, a transaction may be marked hold, which makes it ineligible for execution until the hold flag is cleared. A transaction may be held or released at any time by an Arbortext Publishing Engine administrator using the Transaction List web page. A transaction may also be automatically held by a queue that is configured to do so. If a transaction is executing, setting its hold flag will have no effect unless the Arbortext Publishing Engine is restarted before the transaction finishes executing. If the Arbortext Publishing Engine is restarted, the hold flag will prevent the Queued Transaction Scheduler from executing the transaction. Transaction configuration and administrative actions are explained in Configuration Guide for Arbortext Publishing Engine.