Dispachert robot

What type of process is recommended for a dispatching robot, transactional, linear, iterative, sequential?

1 Like


Linear: Data is fetched once and processing is done once.

Iterative: Data is fetched in bulk and processing is done iteratively.

Transactional: Here data fetching and processing are independent from one another as they are split into different states. In iterative if a single data point results in a failure, whole workflow can fail but in transactional as transactions are independent of one another a single data point never results in breaking down of complete workflow.

Sequential : Sequential processes are reliable if we want the steps to be executed in a specific order.

Type of process depends on the scenario is what I would say
But typically Dispatcher bot is designed for transactional or sequential processes

Dispatcher Robot primarily handles transactional processes. It’s responsible for interacting with systems or applications to gather data or transactions that need to be processed. It typically collects these transactions in a structured manner, like putting them into a queue or data source. These transactions are then processed by other robots, such as Performer Robots.

Sometimes Dispatcher can also follow a sequential or linear process. It collects data or tasks one after the other, following a predefined order or logic. For example, it may gather data from different sources sequentially and then hand it off for further processing in the same order.

So it depends

Cheers @alexis.mendoza.rpa

Typically a dispatcher would be linear - run, load the file into the queue, stop. It could also be iterative if you have multiple files to be loaded for each run of the automation - run, loop over the files in the folder and load each one into the queue.