Turn broken workflow alerts into clear recovery runbooks

Transforms error notifications and technical workflow notes into a simple, step-by-step recovery guide for non-technical team members.

You getSummary of What Failed, immediate Containment Steps and step-by-Step Fix and Re-run Guide

Prompt

Prompt
Act as an operations systems specialist. Turn the pasted workflow error alert and setup notes into a clear, step-by-step recovery runbook that any team member can follow without engineering help.

Rules:
- Identify the root cause in plain English with zero unexplained jargon.
- Provide an exact 3-step checklist to pause or contain the failure so duplicate actions do not occur.
- List sequential recovery steps to fix the issue, re-run missing records, and verify success.
- Specify who needs to be notified if the fix does not resolve the issue within 15 minutes.

Output format:
1. Summary of What Failed
2. Immediate Containment Steps
3. Step-by-Step Fix and Re-run Guide
4. Verification Checklist
5. Escalation Path

Here are the workflow error details and notes:

Example output

Example for: Shopify to Airtable sync error notification

1. Summary of What Failed

The sync that moves new online orders from Shopify into Airtable failed because a customer did not provide a phone number, but the Airtable field was set to require one. New orders are paused in queue.

2. Immediate Containment Steps
  1. Log into Make or Zapier and turn off the active Shopify to Airtable scenario.
  2. Do not manually import the failed order via CSV yet to avoid duplicate rows.
  3. Post in the internal operations Slack channel that order ingestion is temporarily paused.
3. Step-by-Step Fix and Re-run Guide
  1. Open Airtable, go to the Orders base, and find the Phone Number field header.
  2. Right-click the field header, select Edit Field, and uncheck "Require an entry". Save changes.
  3. Go back to Make or Zapier, open the failed execution log, and click "Re-run with original data".
  4. Confirm the record status changes to green/success.
  5. Turn the automated scenario back on.
4. Verification Checklist
  • Check Airtable to confirm the missing order is now present.
  • Verify customer email and shipping address match the Shopify receipt.
  • Check that the next incoming order processes automatically.
5. Escalation Path

If the re-run fails with an authentication error, contact the Lead Systems Administrator in the team channel with the execution ID number.

Written by AI from this prompt. Your results will vary.

Paste your error notification, error log, or tool screenshot text right after the prompt in ChatGPT, Claude, or Gemini. As a follow-up, ask the model to draft an automated customer communication in case records were delayed.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Automation & Workflows