Request Queue

From Commander4j
Revision as of 21:35, 26 August 2024 by Dgarratt (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

When you use one of the transactions within the application which has a output message defined for it the application will put a request in a queue. This queue holds a list of all the unprocessed messages and is polled by the Interface process. When the interface process is running the queue is normally empty. However if the interfaces are not running then all requests for output messages will be held in this queue until the interfaces are started again.

When messages have been processed you can check their status in the Interface Log.

The transactions which generate outbound messages are defined in Interface Admin and many of them depend on being enabled in the Locations screen.

Each item in the request queue will be assigned a unique Request ID and include a Transaction ID which links to the Pallet History table.