As you can see in the question they are processing the second transaction item.
MaxRetryNumber = 1
that means Second transaction going to be retried again

attempts to retrieve a transaction item
from a specified source (e.g., Orchestrator queues, spreadsheets, databases, mailboxes
or web APIs)

If an Orchestrator queue is used and a transaction item fails due to a System Exception,
the path of the screenshot is saved in the Transaction Item Details.

Dispatcher is used to add Queue Items to an Orchestrator Queue Performer should be created in the REFramework

New – the item has just been added to the queue with the Add Queue Item activity, or the item was postponed, or a deadline was added to it, or the item was added after an attempt and failure of a previous queue item with auto-retry enabled.
In Progress – the item was processed with the Get Transaction Item or the Add Transaction Item activity; when an item has this status, your custom progress status is also displayed, in the Progress column;
Failed – the item did not meet a business or application requirement within the project and was therefore sent to a Set Transaction Status activity, which changed its status to Failed;
Successful – the item was processed and sent to a Set Transaction Status activity, which changed its status to Successful;
Abandoned – the item remained in the In Progress status for a long period of time (approx. 24 hours) without being processed;
Retried – the item failed with an application exception and was retried. After the Robot finishes retrying the item, the status changes to Failed or Successful, according to your workflow.
Deleted – the item has been manually selected from the Transactions page and marked as deleted; an item with this status can no longer be processed.

the value for the number of retries is obtained from the constant RetryNumberGetTransactionItem in the config file. This value specifies how many times the Get transaction Item Activity should be retried in case of an exception and it must be an integer that is greater than or equal to one.

Assets Sheet We can create different values for the application path

In Progress – the item was processed with the Get Transaction Item or the Add Transaction Item activity; when an item has this status, your custom progress status is also displayed, in the Progress column;

Constants: Values that are supposed to be the same across all deployments of
the workflow. For example, the department name or the bank name to be used
as input in a certain screen.
If the process does not use a queue, then it is safe to delete this
row and change the value of MaxRetryNumber in the Constants sheet to an
integer greater than zero. This indicates the number of times a robot should retry
a transaction that fails with a system exception

InitAllSettings.xaml file will be executed only once in the beginning

MaxConsecutiveSystemExceptions, which specifies the maximum number of consecutive System Exceptions allowed before stopping the job.

TransactionItem single item for e.g single row
TransactionData Collection of Item Data table

Remove the Get Transaction Item activity from the GetTransactionData workflow.
Add read range activity to read data from a local Excel file in the GetTransactionData workflow.

The Description column offers an explanation about the row, but it is not included in the dictionary

For example, if there is an asset in Orchestrator called CountryName, there can be a row
in the Assets sheet whose Name is CountryAsset and whose Value is CountryName.
During the initialization phase, the framework retrieves the contents of the
CountryName asset and inserts it as a value corresponding to the key CountryAsset in
the Config dictionary.

Must be 0 if working with Orchestrator queues. If > 0, the robot will retry the same transaction which failed with a system exception. Must be an integer value.

Adds a collection of items from a specified DataTable to a specified queue in Orchestrator. Once added to the queue, the items‘ statuses are changed to New.

Abandoned – the item remained in the In Progress status for a long period of time (approx. 24 hours) without being processed;

Gets a specified Orchestrator credential by using a provided AssetName, and returns a username and a secure password.

Initialization: Read the configuration file and initialize the applications used in the process. If the initialization is successful, the execution moves to the Get Transaction Data state; in case of failure, it moves to the End Process state.

Abandoned – the item remained in the In Progress status for a long period of time (approx. 24 hours) without being processed;

A Business Exception describes an error rooted in the fact that certain data which the automation project depends on is incomplete or missing.
Such a situation is, for example, a project which extracts phone numbers from an employee database, creating queue items for each of them. These items are then to be processed and inserted into a financial application. If a certain phone number is missing a digit due to human error, the queue item containing it becomes invalid. This causes the automation to throw an exception,

Get Transaction Data is the data retrieval state, which is used to get the transaction from the queue, data table, folder, database, and other sources. In our example, it looks for any transaction items in the Orchestrator Queue to process.
REFramework pre-built functionality looks for a Stop Request and will stop the process even though there are items still in the queue to process. This becomes helpful in situations where you want to correctly stop a process and free up the Robot to run a different job.

Although the Assets sheet can be used for most types of assets, it cannot be used fo assets of type credential, since credentials have two values: username and password.
To use credential assets defined in Orchestrator, include them in the Settings sheet instead

Dealing with Incorrect Data Handled by Business Exception
Please note Business Exception data will not be retried
so it will go to Get Transaction Data for New Transaction

For E.g.
names of queues, folder paths or URLs for web systems.

main argument is
in_TransactionItem, which represents the piece of data to be processed.

Place all the activities and logic needed to process one transaction in the process workflow.

The value of the Max # of retries on the queue is 2 is overwritten

MaxConsecutiveSystemExceptions to 2

Use the Get Credential activity to retrieve the credential from Orchestrator.

Queue Item Failed with Business Exception will be never retried

For E.g , the department name or the bank name to be used as input in a certain screen.

After Add Queue Item-New
After Get Transaction Status-In Progress
After Postpone Transaction Item-New

When Adding Queue Item Status is “New“
When Get Transaction Item executed status is “In Progress“

SetTransactionStatus.xaml, this workflow is called
after the Process.xaml workflow is executed, and it sets the status of the transaction
according to the result of the processing step.

MaxConsecutiveSystemException Config parameter allows developers to set a maximum number for allowed consecutive system exceptions

Queue Item Updated in 2 States
GetTransactionData.xaml
SetTransactionStatus.xaml

KillAllProcesses.xaml used to force close all the application in case of CloseAllApplication Fails

Values that are supposed to be the same across all deployments of the workflow.
For E.g., the department name or the bank name to be used as input in a certain screen.

First Take Screenshot
Then
Set Transaction Status
Then
Closing All Applicaiton
Finally
Initall Application

Successful – A job is in this state if it has been executed correctly by the Robot and it has finished running or has been stopped using the Stop button.
 Faulted – A job is in this state if it failed to start or the process threw an unhandled error during execution.
Stopping – An intermediary state that is triggered if you click the Stop button in Orchestrator. The job is canceled as soon as it is safe. This can be implemented in a workflow using the Should Stop activity.
Suspended – An intermediary state that is triggered with the purpose of allowing user intervention or completion of an intermediary process. It is triggered by the corresponding activities in Studio.

Used in case transactions arestored in a DataTable, forexample, after being
retrieved from a spreadsheet.

To disable this feature, the value of the constant should be set to 0.

MaxRetryNumber, which specifies how many times a robot attempts to retry processing a transaction that failed with a system exception

Although the Assets sheet can be used for most types of assets, it cannot be used for
assets of type credential, since credentials have two values: username and password. To
use credential assets defined in Orchestrator, include them in the Settings sheet instead

in_TransactionItem data type of QueueItem holds the transaction information

Dispatcher = Producer
The dispatcher process pushes transaction items to an Orchestrator queue. It extracts data from one or multiple sources and uses the same to create queue items for Performer robots to process.
Information is pushed to one or more queues allowing the dispatcher to use a common format for all data stored in queue items.
Performer = Consumer
The performer process pulls transaction items from an Orchestrator queue and processes them as needed by the company. Queue items are processed one at a time.
It uses error handling and retry mechanisms for each processed item.
A major advantage of the performer is its scalability (multiple performers can be used with a single queue).
The advantages of the Dispatcher and Performer model:
Better separation of actions (between dispatcher/producer or performer/consumer).
Better separation and distinction between architecture and process layers.
Better error handling and retry mechanism.
Possibility to run processes across several machines (availability).
Better reusability within the project‘s created components.
Improved built-in configuration and Orchestrator integration.
Automation projects created previously without ReFramework can be easily adapted and deployed using the Dispatcher and Performer model.

REMOVE
Remove removes the text that we describe in the logic (inverse to SUBSTRING)
Deleting content 5 characters from the first character from the left (0)

Sequences are the smallest type of project. They are suitable to linear processes as they enable you to go from one activity to another seamlessly, and act as a single block activity.
One of the key features of sequences is that they can be reused time and again, as a standalone automation or as part of a state machine or flowchart.