docs(aws-serverless): Backport improved troubleshooting execution guide#160
docs(aws-serverless): Backport improved troubleshooting execution guide#160vishalsatam wants to merge 1 commit into
Conversation
5e2f55c to
42cf189
Compare
bchampp
left a comment
There was a problem hiding this comment.
I think we might consider adding a little more explicit instructions in the "Identify the root cause". From the original GitHub issue:
Key events to look for:
- CallbackTimedOut — timeout fired but may not have been caught
- ContextFailed — child context threw an unhandled error
- ExecutionFailed — entire execution crashed
- CallbackStarted with Timeout field — confirms timeout was registered
What do you think? Right now we're relying on the agents ability to interpret these history events but I think we can provide clearer guidance.
42cf189 to
039881e
Compare
I updated the commit to include details for the failure type of events. |
Backport changes from aws/aws-durable-execution-docs#161 to the agent-plugins repo. Improvements include: - ARN-based workflow instead of separate function name + execution ID - Alias resolution and list executions step - Console link generation for visual debugging - Structured output format with clear diagnosis summaries - CloudWatch Logs querying when execution history is insufficient - Additional usage examples covering failure scenarios - Better error handling guidance (execution not found, permissions) - Expanded trigger keywords in SKILL.md for better routing Closes aws/aws-durable-execution-docs#162
039881e to
2478a8b
Compare
|
@scottschreckengaust @theagenticguy @krokoko , can you please review this pull request? If you approve, please merge as well since I don't have permissions. |
Backport changes from aws/aws-durable-execution-docs#161 to the agent-plugins repo.
Improvements include:
Closes aws/aws-durable-execution-docs#162
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.