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
- Features
- Exceptions and correction
Exceptions and correction
Assign corrective work while retaining the prior run and revision evidence.
OverviewApproved revision decisions×
RPA Task Manager · Exceptions and correction
New
Approved revision decisions
Review decisions
| Source | Source revision | Decision | Decided at | Reviewer | |
|---|---|---|---|---|---|
| BD-60776 | 720 | Approved | 26 Oct | ||
| BD-20938 | 940 | Approved | 10 Oct | ||
| BD-71023 | 560 | Approved | 14 Oct | ||
| BD-48930 | 790 | Approved | 11 Oct | ||
| BD-89057 | 650 | Approved | 16 Oct |
6 of 6 records
BD-60776Review decisions · RD-53278
ApprovedSource revision720
Decided at26 Oct
What you can do
Correct without losing the earlier result
When a run fails or produces an uncertain result, the Exception Coordinator can assign a follow-up action against the bot definition. The action has a title, assignee, due date, status, completion date and resolution. Operators can use the attempt failure reason, operation status, numbered steps and supporting documents to explain what happened before choosing a correction.
The correction workflow handles an executed revision without deleting its evidence. It records a correction run and compensating output, keeps the prior revision and completed steps, creates a successor revision, raises a verification follow-up and appends status history. The successor can be reviewed as its own revision. This makes the original execution and the corrective work distinguishable in the record.
How the work is organized
- Action. A named assignee and due date keep an exception visible until its resolution is recorded.
- Investigation. Attempts, operations and receipts show which external action completed or remains uncertain.
- Successor. A new revision carries corrected work forward while the earlier trace remains available.
What to agree during setup
Define which failed or uncertain outcomes create a follow-up action and who assigns it. Decide when a provider result should be reconciled before a compensating action is attempted. Agree who verifies the correction, what evidence must accompany its resolution and when a follow-up may be marked Completed or Cancelled. Keep the ownership rule clear when the person investigating is also the owner of the original bot.
Consider an extract bot that completes a provider action but applies the wrong mapping. The coordinator opens a follow-up for the owner. The operator traces the original step and its receipt, records the compensating output, then creates a successor revision with the corrected mapping. The original completed step stays readable. The reviewer examines the successor, while the coordinator closes the action only after the documented resolution matches the confirmed result.
Check the handoff on an actual case
Start from one failed attempt or an operation requiring reconciliation. Find its parent definition, revision and operation key. Assign a follow-up to a person and record a due date. Rehearse a correction and check that the original operation and receipt still open from the prior revision. Follow the new revision to its verification task. Close the action with a resolution that names the outcome rather than only changing its status.
What your team sees
- Open corrective actions — Assigned work still Open or in progress.
- Execution attempts requiring attention — Failed and uncertain attempts needing investigation.
Follow the work through
What it keeps track of
Data model- Follow up actions
- Open corrective work raised against an automation exception.
- Bot definitions
- Versioned automation definitions scheduled against a queue.
- Execution attempts
- Individual attempts made while executing a bot definition.
- Operation runs
- Workflow-maintained execution records with frozen revision and input hash.
- Operation steps
- Ordered numbered steps with persisted input/output identities.
- Bot runs
- Observed run results reported against a bot definition.
- Evidence documents
- Supporting documents and external references captured for a run.
- State history
- Immutable status transitions written by automation workflows.
- Review decisions
- Independent review decisions recorded against a bot definition revision.
Who uses it
Permissions- Exception Coordinator
- Assigns and resolves follow-up; Automation Operator investigates and corrects; Bot Reviewer examines the successor revision; Operations Analyst reads the outcome.
Set up RPA Task Manager your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.