Publishing Engine Programmer's Guide > The Arbortext Publishing Engine Request Manager > Predefined Dynamic Components > Pre-Defined Queues > Holding and Releasing Transactions
  
Holding and Releasing Transactions
A queued transaction may be held or released. When held, no Arbortext queue will present the transaction to the Queued Transaction Scheduler for execution. By default, a transaction is not held when it is placed on a queue. 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.
If the queue parameter hold-all is set to yes in e3config.xml, then the Arbortext Queue it controls will hold each transaction it accepts.