Transaction States
A transaction can exist in one of a number of distinct states during its lifecycle.
• initializing
The Arbortext PE server is receiving the request.
• waiting
The transaction is waiting to be allocated to an Arbortext PE sub-process (for immediate requests).
• queued
The transaction was placed in a queue and is waiting to be executed by the Queued Transaction Scheduler.
• processing
The transaction is being executed by an Arbortext PE sub-process.
• +
complete
The transaction is finished. A completed transaction can be completed successfully or completed with errors. Note that if the results is an error report rather than the expected document, the transaction is still considered complete.
A transaction can also expire while waiting for an Arbortext PE sub-process allocation (if it’s an immediate transaction).
• cancelled
The transaction has been cancelled.
The transaction lifecycles are as follows:
• An immediate request transaction follows the lifecycle:
Initializing ⇒ Waiting ⇒ Processing ⇒ Complete
• A queued request transaction follows the lifecycle:
Initializing ⇒ Queued ⇒ Processing ⇒ Complete or Cancelled
A completed transaction may be available in the Transaction Archive if it meets the archiving criteria. Refer to
Using the Transaction Archive for more information.