# Failed Automation Recovery Worksheet

By Kashif Rehman | BizThrivers | November 8, 2026
https://bizthrivers.com/resources/failed-automation-recovery-worksheet/

Free to adapt. Use sample values; do not place credentials or customer records in this worksheet.

## Planning decisions

### Which process and case need attention?
Give the incident one reference, such as HEAT-08. Record the business/location, workflow and version, affected step, first observed time, timezone and affected window. Keep customer details in the approved business system; use a private record reference here.
Your decision: 

### Who owns the next decision?
Name one incident owner, a trained recovery operator, a decision approver and a backup. Agree who contacts the customer if needed. The owner must accept the case and state the next staffed review time; copying several people is not an assignment.
Your decision: 

### What is done, missing or still unknown?
Compare the relevant execution history with the actual destination: conversation, booking, task list or connected service. Record what each source proves and when it was checked. A missing confirmation is Unknown until someone can verify the outcome.
Your decision: 

### What must be held before another attempt?
Ask the authorized operator to identify and verify the specific record, queued action or linked process that needs containment. Record Stop requested separately from Stop verified. Changing this sheet, acknowledging an error or assuming a status switch worked does not establish a stop.
Your decision: 

### What exact recovery and closure are approved?
Choose Hold, Complete only missing work, Authorized retry or Escalate. State the exact action and records, already-completed work that must not repeat, one operator, approval evidence, a deadline and the observed result required for closure. Unknown results go back to hold.
Your decision: 

## One failure, one recovery decision
Case reference / business / location: 
Workflow / version / affected step: 
First observed / timezone / affected time window: 
Incident owner / accepted at / backup: 
Next staffed check / escalation deadline: 

## Evidence before touching the record
Keep customer details and credentials out of this shared worksheet. Use private references to the approved business system.
| Step / intended outcome | Log says / checked at | Actual destination says / checked at | Done / Missing / Unknown | Evidence reference |
| --- | --- | --- | --- | --- |
| Earlier action | | | | |
| Failed or uncertain action | | | | |
| Later action | | | | |

## Containment and customer handling
Further retries requested to stop / by / at: 
Specific record, queued action or connected process to hold: 
Actual control used by authorized owner: 
Stop verified by / at / evidence: 
Still-running or unverified work / escalation: 
One customer-contact owner / contact needed / approved wording: 
A request or an edited worksheet is not proof that the real process stopped.

## Recovery decision
Choose: Hold for evidence / Complete only the missing work / Authorized retry / Escalate.
Exact action and affected record(s) authorized: 
Already-completed actions that must not repeat: 
Required permission, consent, cost or data check: 
Approver / decision evidence / approved at: 
Single operator / allowed time / maximum one agreed attempt: 
If the result is still unknown: hold and escalate; do not retry blind.

## Recovery and closure log
| Case / approved action | Operator / at / timezone | Observed result in actual destination | Duplicate check | Next decision / owner |
| --- | --- | --- | --- | --- |
| | | | | |

## Copyable internal handoff
Case [reference]: [process] needs review. The last confirmed outcome is [fact and evidence location]. The uncertain or missing action is [one action]. Further retries are on hold [verified state or explicit unknown]. [Owner] owns the decision by [time and timezone]; [backup] covers absence. Please choose hold, complete only the missing work, authorize one exact retry, or escalate. Replace the brackets manually.

## Close only after an observed check
Controlled test / result / checked by: 
Original affected case reconciled / evidence: 
Outstanding customer or data correction / owner: 
Fix version / rollback or stop owner: 
Operating owner accepted / at: 
Next staffed review / open cases remaining: 

## Observed test record

### 1. Correct case, step and time
Action: Use a controlled sample and compare its private reference, workflow, affected action, time window and timezone with the evidence. Add a second similar sample so the reviewer must distinguish them.
Expected: The owner identifies the correct case and action. A similarly named record or a different time window is not used as evidence.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 2. Stop requested is not stop verified
Action: In a harmless test or tabletop exercise, ask the operator to hold only the agreed work. Record the request and the evidence of the actual held state separately; list anything still unverified.
Expected: The actual containment state is checked. Unknown queued or linked work is escalated; an edited worksheet is not treated as a stop.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 3. Completed work stays completed
Action: Model an enquiry where the confirmation email arrived but a staff task is missing. Compare both destinations and ask the approver to identify only the missing action.
Expected: The received email is preserved as completed. The missing task has a separate recovery decision; the whole sequence is not replayed.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 4. An uncertain result stays on hold
Action: Use a tabletop scenario in which a connected service times out and its records cannot be checked. Ask the owner what they can honestly conclude and who can obtain the missing evidence.
Expected: The outcome remains Unknown. No blind retry is approved while the destination cannot be verified; one owner seeks the evidence.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 5. One approved recovery attempt
Action: With harmless sample records, have two staff receive the same request. Ask them to find the shared case and verify who alone is authorized to perform the exact recovery.
Expected: One operator owns the approved action. Others check the same case first; a repeated request does not become another attempt.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 6. Backup and observed closure
Action: Make the main owner unavailable in a tabletop exercise. Have the backup accept the case, state a review time and identify the controlled retest plus original-case checks needed before closure.
Expected: A backup explicitly accepts the case. Closure needs an observed recovery result and original-case reconciliation, not a cleared badge.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

## Release and handover
Outstanding fixes: 
Operating owner: 
Approver and decision: 
Review date: 
Where to monitor and how to pause a problem: 
Change-request route: 

## Sources checked November 8, 2026
https://help.gohighlevel.com/support/solutions/articles/155000003992-execution-logs-enrolment-history-enhancements
https://help.gohighlevel.com/support/solutions/articles/155000009464-review-workflows-with-errors
https://help.gohighlevel.com/support/solutions/articles/155000003065/
https://help.gohighlevel.com/support/solutions/articles/155000009497-how-to-use-workflow-maps-in-highlevel

A completed log records your observations. It does not automatically verify the CRM or agent.
Independent HighLevel affiliate: I may earn a commission through referral links on BizThrivers.