Appian RPA Workflow: Catch Run time Exception from low code components

Mukesh,

You have a couple of options here with low-code when a robotic process execution has an unexpected failure. These options expect that one execution of your robotic process correlates to one item. We recommend using this pattern and using Appian process models to orchestrate the executions.

1. You can use our OOTB exception handling capabilities with RWM. You can configure who is assigned a case upon failure in a decision table. That person or group would automatically receive an email notification shortly after the failure occurs. When they open up the task in Appian, they would see the details of the execution, and be provided a link to the execution log.

2. You can build custom logic into your process model to orchestrate the RPA work. Use the following design pattern:

• Use a process model to launch your RPA execution
• Use the Execute Robotic Process smart service and pass in inputs to the robot
  • This node will pause as the robot is executing and will then return the result
  • Within the Node Outputs, you can define a variable to capture the status of the execution
  • Have a decision node within your process model to go through the following nodes upon exception
• (optional) Create an integration object in your process model that calls the Get Execution Trace endpoint to retrieve the trace of the execution
• Use the send email smart service node to send an email with the details of the execution, including the trace if desired

Frank

Mukesh,

You have a couple of options here with low-code when a robotic process execution has an unexpected failure. These options expect that one execution of your robotic process correlates to one item. We recommend using this pattern and using Appian process models to orchestrate the executions.

1. You can use our OOTB exception handling capabilities with RWM. You can configure who is assigned a case upon failure in a decision table. That person or group would automatically receive an email notification shortly after the failure occurs. When they open up the task in Appian, they would see the details of the execution, and be provided a link to the execution log.

2. You can build custom logic into your process model to orchestrate the RPA work. Use the following design pattern:

• Use a process model to launch your RPA execution
• Use the Execute Robotic Process smart service and pass in inputs to the robot
  • This node will pause as the robot is executing and will then return the result
  • Within the Node Outputs, you can define a variable to capture the status of the execution
  • Have a decision node within your process model to go through the following nodes upon exception
• (optional) Create an integration object in your process model that calls the Get Execution Trace endpoint to retrieve the trace of the execution
• Use the send email smart service node to send an email with the details of the execution, including the trace if desired

Frank