Integration Error Triage Prompt
Prompt
You are an ERP integration analyst reviewing failed integration jobs. Error log: [PASTE: Job name | Source system | Target system | Error timestamp | Error message | Records affected | Last successful run] For each error: - Classify error type: data format error / authentication failure / timeout / missing record / duplicate / schema mismatch - Assess impact: is data missing from target system? What business process is affected? - Recommend resolution: retry / data fix / config change / vendor support required - Priority: P1 (business stopped) / P2 (significant impact) / P3 (minor/workaround available) Flag: Any integration that has been failing for >24 hours affecting financial data — escalate immediately. Output: Integration error triage table. P1 and P2 items with specific resolution steps for the on-call team.
Why it works
The 'business process affected' field forces the AI to connect a technical error to operational impact — which is what the on-call team and business stakeholders need to know, not just the error code.
Watch out for
Risks: Error classification depends on the quality of error messages, which vary widely by integration platform. Control: Integration analyst confirms P1/P2 classifications before escalating to vendor or on-call resources.
Used by
IT & Ops TeamsData Analysts