Skip to content

docs: Expand troubleshooting event types for root cause diagnosis#184

Merged
bchampp merged 1 commit into
aws:mainfrom
vishalsatam:feature/expand-troubleshooting-event-types
May 15, 2026
Merged

docs: Expand troubleshooting event types for root cause diagnosis#184
bchampp merged 1 commit into
aws:mainfrom
vishalsatam:feature/expand-troubleshooting-event-types

Conversation

@vishalsatam
Copy link
Copy Markdown
Contributor

Sync expanded event type documentation from awslabs/agent-plugins#160.

Adds detailed event type guidance to step 2b of the troubleshooting execution guide, giving agents explicit instructions on which history events to look for:

  • Execution-level failures (ExecutionFailed, ExecutionTimedOut, ExecutionStopped)
  • Context and step failures (ContextFailed, StepFailed with RetryDetails)
  • Callback issues (CallbackStarted, CallbackTimedOut, CallbackFailed)
  • Chained invocation failures (ChainedInvokeFailed/TimedOut/Stopped)
  • Other signals (WaitCancelled, InvocationCompleted with Error)

This was added based on review feedback in the agent-plugins backport PR and should be synced back here.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

Add detailed event type documentation to step 2b of the troubleshooting
guide, providing explicit guidance on key execution history events:

- Execution-level failures (ExecutionFailed, ExecutionTimedOut, ExecutionStopped)
- Context and step failures (ContextFailed, StepFailed with RetryDetails)
- Callback issues (CallbackStarted, CallbackTimedOut, CallbackFailed)
- Chained invocation failures (ChainedInvokeFailed/TimedOut/Stopped)
- Other signals (WaitCancelled, InvocationCompleted with Error)

This gives agents clearer guidance for interpreting execution history
events rather than relying on implicit knowledge.

Syncs with awslabs/agent-plugins#160.
@bchampp bchampp merged commit a575cba into aws:main May 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants