On-Demand Retry

The valid requests which are not executed successfully are re-triable from the transactions view. The following type of transactions are re-triable:

· Transactions that have timed out before even being picked up by the robot. Such transactions are available in the Overflow tab.

· Transactions that have timed out while being executed by the robot. Such transactions are available in the Failure tab.

· Transactions that have encountered an exception while being executed. Such transactions are available in the Failure tab.

To retry the transactions:

1. In the Transaction View details> Click the (Retry) icon.

2. If required, one or more input fields can be corrected before retrying the request. For rest of the fields where correction is not required, values from current node of the transaction are reused by checking the <User input values of current transaction for empty fields>.

3. Click the (Multiple Retry) icon to retry the multiple transactions at once. Currently the limit is set to 10 for on-demand retry of multiple transactions.

Following are the key points to consider for on-demand retry capability:

· Only the latest node of the transaction is retriable. Once the request is successfully executed, it cannot be retried. For example, if a failed request is retried manually, and on this occasion, it encountered an exception while being executed, only the latest node which encountered an exception is manually retriable.

· In case, the transactions are marked for automatic retry, the transaction are manually re-triable only after automatic retry attempts are exhausted.

· Multiple transactions are re-triable at once. Currently the limit is set to 10 for on-demand retry of multiple transactions. In case more than 10 transactions have to be retried, requests can be retried in batches of 10.