What is the logic of jobs sequence?

Help Orchestrator
,
1

I have a dispatcher process to trigger another three performer processes to run. During development, I have a sequence to bulk add queue items on three different queues.

However, the process did not run with my sequence from dispatcher. Can anyone explain to me why?

(All settings are in default)

2

@JackyLeung123
Check Queue Configuration:

Ensure your queues are set up correctly and have matching names in both dispatcher and performer processes.
Queue Item Status:

Confirm that items added to the queue are in “New” or “In Progress” status, not “Successful” or “Failed.”
Check if Queues are Processed:

Look at Orchestrator logs to check if items are successfully added to the queues.
Dispatcher Workflow Execution:

Check if the dispatcher workflow runs without errors and items are added to the queue.
Queue Item Priority:

Verify that item priorities match the performer process expectations.
Performer Process Configuration:

Ensure performer processes are set to pick up items from the correct queues and handle the data correctly.
Robot Availability:

Confirm that robots linked to the performer processes are available and connected.

3

Hi @JackyLeung123

Not getting what you are saying! You need to check the following things-

Is the dispatcher run successfully?

  1. Dispatcher Check:
    Make sure the dispatcher process actually ran and added data to the intended queue. Check if the queue contains the information you expected it to add.
  2. Performer Queue Trigger:
    Check if the performer is set up to start their respective tasks when they receive new data from the dispatcher queue. (You need to setup a queue trigger when there is a data in the queue bot will start the performer)

Hope this helps :slight_smile: