Agent Execution Outage Client Notification Spec

Role: Principal AI Reliability Engineer and Client Systems Lead

Context

• Impacted enterprise client: {{client_name}}
• Name of affected autonomous pipeline: {{agent_workflow_name}}
• Subsystem or API tool encountering errors: {{failing_tool_name}}
• Identified root failure mechanism: {{schema_error_cause}}
• Active deterministic mitigation: {{fallback_strategy}}
• Projected resolution timeline: {{remediation_eta}}

Task

Draft a comprehensive client email specification detailing the disruption in the autonomous agent workflow, explaining technical root causes without unnecessary jargon, and outlining active recovery workflows to restore full production confidence.

Method

1. Review the operational impact of the failing tool on downstream workflow steps in {{agent_workflow_name}}.
2. Translate the technical root cause from {{schema_error_cause}} into actionable client-facing impact statements.
3. Detail the fallback orchestration mechanism {{fallback_strategy}} active during the degraded state.
4. Formulate the required communication posture based on {{client_name}} service level agreements.
5. Draft the complete email structure including subject line, executive summary, and technical impact section.
6. Insert concrete recovery milestones anchored to {{remediation_eta}}.
7. Define explicit follow-up cadence and immediate developer actions for client engineering teams.

Constraints

• MUST keep the core email draft under 400 words.
• MUST NOT expose internal API tokens, raw stack traces, or proprietary runtime parameters.
• MUST clearly differentiate between agent-level decision errors and upstream API timeouts.
• All timestamp commitments must reference {{remediation_eta}} precisely.
• Use unambiguous, professional engineering tone.

Output format

Provide the specification in four ordered markdown sections:

1. Email Header (Subject line options, sender persona, urgency tier)
2. Executive Summary (High-level business impact statement)
3. Technical Incident Breakdown (Affected tool calls, active fallbacks, timeline)
4. Client Action Items (Required settings adjustments or verification steps)

Self-review

• Confirm {{failing_tool_name}} and {{fallback_strategy}} are explicitly detailed.
• Verify all MUST constraints are met and tone remains accountable.
• Ensure no unparsed template variables or generic filler phrases remain.