Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


The Queue Management feature in Adeptia Connect allows you to manage and regulate the execution of Transactions, Templates, and Process Flows. You can create a dedicated queue for the execution of Transactions associated with a Partner on a dedicated runtime instance. You can also run a specific set of Transactions, Templates, or Process Flows that are not associated with a particular Partner, on a dedicated runtime instance by using Queue Management. A queue that you may have created can be edited or deleted at any point in time. 

When you create a queue, a new runtime service also gets up at the same time, and it starts accepting the transactions from that queue to process them. 

Write steps for creating/editing/deleting queues from Queue Management.


It regulates the execution by:

The Queue Processor executes process flows based on the priority information associated with each process flow. You have the following priority levels available to set for a process flow: 

  • Real Time Processing
  • High
  • Medium
  • Low 

Any process flow with 'Real Time Processing' priority bypasses the Queue Processor and is executed immediately. The following types of process flows also qualify to be executed immediately bypassing the Queue Processor:

  • Process flows associated with Web Services
  • Process flows with an Event that has Trigger in Sequence as checked
  • Child process flows (except for Spawn action with 'Wait For Child as False')

Process flows with High, Medium, and Low priority are executed by the Queue Processor. The order of execution of process flows based on the priority is as follows:

  1. High
  2. Medium
  3. Low

Process flows with same priority level are executed on first-in, first-out (FIFO) basis. 

Refer to the section Defining Priorities for Process Flows to know how to set the priority. Adeptia recommends you to set the priority for your process flows in such a way that none of them remains in the queue for a long time. This is also to mitigate any risk of low or medium priority process flows not being executed at all. 

The priority levels 'Immediate' and 'Normal' for process flows defined in the previous version of Connect will be considered as 'Real Time Processing' and 'Low' priorities respectively. 

Setting up the number of concurrent process flows execution

Through environment varaible.

See also

/wiki/spaces/AC40/pages/3181249

You may be interested in...
What's new
Best practices
Training guides
/wiki/spaces/AC40/pages/3180519
/wiki/spaces/AC40/pages/3181640
Adeptia security report
  • No labels