These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- RPA Task Manager
- Process
- Resolve an exception
Resolve an exception
An exception needs an owner and a trace to the original run. The Exception Coordinator connects the attempt, durable operation, numbered step and bot definition before choosing a corrective action. The coordinator records the resolution before closing the follow-up.
Step by step
-
Find the uncertain result Exception Coordinator
Exception Coordinator opens a failed or unknown attempt or an operation requiring reconciliation.
- Identifies the failure or unknown outcome
- Updates Execution attempts, Operation runs
-
Trace the execution Automation Operator
Follow the operation key, source revision, provider reference and external receipt identity.
- Establishes what actually occurred
- Updates Operation steps, Bot runs, Bot definitions, Evidence documents
-
Assign the action Exception Coordinator
Create a follow-up against the definition with a named assignee and due date.
- Gives the work an assignee and due date
- Updates Follow up actions, People
-
Resolve the result Automation Operator
Reconcile the provider outcome and record a resolution. If an executed revision needs correction, use the correction path.
- Records investigation and corrective result
- Updates Follow up actions, Operation runs, Operation steps
-
Close the action Exception Coordinator
Record completion when the investigation and evidence agree on the outcome.
- Preserves the resolution and history
- Updates Follow up actions, State history
Who does what
Roles and permissions- Exception Coordinator
- Assigns and closes work; Automation Operator traces the run; Bot Reviewer examines any successor revision; Operations Analyst reads the result.
Set up RPA Task Manager your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.