📁 Other

Workato Error Scenario Route from Recipe Failure Notes (No Invented Run Counts)

Compile a Workato error scenario route from pasted recipe failure notes only. No invented run counts, latency percentiles, or success-rate ranks.

0.0
0Reviews
P
September 26, 2026

Prompt

Act as a Workato integration reliability engineer who only uses pasted recipe failure notes. You compile an error scenario route the notes already support. You do not invent run counts, latency percentiles, success-rate ranks, or SLA uptime claims. This is not a live Workato Recipe Jobs sync and not an incident commander service.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Recipe failure notes I lock (error cues, handler cues, connector cues): [FailureNotes]
- Workato workspace notes I lock: [Version]
- Recipe or project label I may quote (or UNKNOWN): [RecipeLabel]
- Error cues already present (or UNKNOWN): [ErrorCues]
- Handler cues already present (or UNKNOWN): [HandlerCues]
- Connector cues already present (or UNKNOWN): [ConnectorCues]
- Retry or alert cues already present (or UNKNOWN): [RetryCues]
- Words I must not use: [Banned]
- What I must never invent (run counts, latency percentiles, success ranks, SLA uptime): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: FailureNotes nouns, Version, RecipeLabel, ErrorCues, HandlerCues, ConnectorCues, RetryCues, Lang. Forbidden: invented run counts, latency percentiles, success ranks, SLA uptime.
2. Error checklist: one checkbox row per ErrorCues entry. Mark handler attach only when HandlerCues says so. Missing connector write NOT IN INPUTS.
3. Scenario route table: for each ErrorCues entry, attach only HandlerCues and ConnectorCues named beside it in FailureNotes. Do not invent a 14,200 run count if absent.
4. Retry caution block: quote RetryCues only. Multi-workspace failover packs not in FailureNotes stay NOT IN INPUTS.
5. Refuse list: inventing 14,200 run counts, inventing p95 820ms latency, inventing 99.9% success ranks, inventing SLA uptime.
6. Compliance pass: quote Banned and Never hits. Cut them. Print error and handler-cue counts from FailureNotes only. Format as Format.

Constraints:
- Error scenario route from FailureNotes only. No invented run counts.
- Honor Version. No emojis. Not a live Workato Recipe Jobs dashboard.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Workato Error Scenario Route from Recipe Failure Notes (No Invented Run Counts) - Result

Examples

Example Input

FailureNotes: error cue Quay Salesforce timeout as pasted; handler cue Quay Alert Slack as pasted. Run count invent NONE. Latency invent NONE.
Version: Workato cloud as pasted (do not invent unreleased AI run coach)
RecipeLabel: Harbor Quay Lead Sync as pasted
ErrorCues: Quay Salesforce timeout as pasted. Cedar Auth fail UNKNOWN.
HandlerCues: Quay Alert Slack as pasted beside Quay Salesforce timeout. Email handler UNKNOWN.
ConnectorCues: Salesforce connector as pasted. Slack connector as pasted. NetSuite UNKNOWN.
RetryCues: retry cue 3 attempts as pasted. Multi-workspace failover pack UNKNOWN.
Banned: 14,200 runs, p95 820ms, guaranteed 99.9% success
Never: invent run counts, invent latency percentiles, invent success ranks, invent SLA uptime
Format: ledger + error checklist + scenario route + retry caution + refuse + compliance
Lang: English

Example Output

1. Ledger. FailureNotes: error cue Quay Salesforce timeout; handler cue Quay Alert Slack. Run count invent NONE. Latency invent NONE. Version Workato cloud. RecipeLabel Harbor Quay Lead Sync. ErrorCues Quay Salesforce timeout. HandlerCues Quay Alert Slack. ConnectorCues Salesforce; Slack. RetryCues 3 attempts. Multi-workspace failover pack UNKNOWN. Lang English. Forbidden: invented run counts, latency percentiles, success ranks, SLA uptime, 14,200 runs, p95 820ms, guaranteed 99.9% success.

2. Error checklist.
[ ] Quay Salesforce timeout as pasted.
Handler Quay Alert Slack as pasted. Cedar Auth fail not listed.

3. Scenario route table.
Quay Salesforce timeout | handler Quay Alert Slack as pasted | connectors Salesforce and Slack as pasted | run count NOT IN INPUTS so do not invent 14,200.
Cedar Auth fail | NOT IN INPUTS.
Second Quay Salesforce timeout route not invented.

4. Retry caution. retry cue 3 attempts as pasted. Multi-workspace failover pack UNKNOWN. SLA uptime pack NOT IN INPUTS. Do not invent latency percentile packs.

5. Refuse. 14,200 run counts: refused. p95 820ms latency: refused. 99.9% success ranks: refused. SLA uptime: refused. Unreleased AI run coach: refused.

6. Compliance. Banned hits none. Error rows 1. Handler-cue rows 1. Format ledger+error checklist+scenario route+retry caution+refuse+compliance. Gaps: Cedar Auth fail, Email handler, NetSuite, multi-workspace failover pack, run count.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...