Improve troubleshooting execution steering guide#161
Merged
Conversation
Expand trigger keywords in POWER.md for better routing to the troubleshooting guide. Rewrite troubleshooting-executions.md with clearer diagnostic steps, ARN-based workflow, console link generation, structured output format, and additional usage examples.
vishalsatam
force-pushed
the
feature/improve-troubleshooting-steering
branch
from
02fb759 to
6260c96
Compare
Contributor
Author
|
Testing prompts |
bchampp
reviewed
May 6, 2026
Member
|
We'll need to backport this to https://github.com/awslabs/agent-plugins/blob/main/plugins/aws-serverless/skills/aws-lambda-durable-functions/references/troubleshooting-executions.md as well. |
yaythomas
reviewed
May 6, 2026
yaythomas
reviewed
May 6, 2026
yaythomas
reviewed
May 6, 2026
|
|
||
| 3. If the command fails: | ||
| - Execution not found: Tell the user the execution ID may be incorrect or the execution may have been purged. Ask them to verify the ARN. | ||
| - Permissions/network error: Suggest checking IAM permissions (lambda:GetDurableExecutionHistory) |
Contributor
There was a problem hiding this comment.
suggestion:
Permissions/network error: check that your caller identity has ambda:GetDurableExecutionHistory on the function ARN. This is not part of AWSLambdaBasicDurableExecutionRolePolicy."
Member
There was a problem hiding this comment.
This is a good point - general note, do we clarify anywhere in the power about the permission model? I think it might be useful to have some context about permissions you need within the lambda loop (e.g. checkpoint, get state - included in AWSLambdaBasicDurableExecutionRolePolicy), and permissions outside of the loop (like this one).
Contributor
Author
There was a problem hiding this comment.
I'll add "Permissions/network error: check that your caller identity has ambda:GetDurableExecutionHistory on the function ARN."
don't think we need to mention "AWSLambdaBasicDurableExecutionRolePolicy" since the user could be signed in with any role.
yaythomas
reviewed
May 6, 2026
yaythomas
requested changes
May 6, 2026
Contributor
Add steps to fetch the log group and query logs filtered by invocation ID and execution name when execution history alone is insufficient to determine root cause.
Add step 0 to resolve function alias to version and list executions when user provides function name instead of full ARN. Also add STOPPED status and improve permissions error guidance.
Contributor
Author
|
Test prompt with cloudwatch logs |
yaythomas
approved these changes
May 6, 2026
bchampp
approved these changes
May 6, 2026
This was referenced May 7, 2026
Closed
Closed
vishalsatam
added a commit
to vishalsatam/agent-plugins
that referenced
this pull request
May 7, 2026
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
vishalsatam
added a commit
to vishalsatam/agent-plugins
that referenced
this pull request
May 7, 2026
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
vishalsatam
added a commit
to vishalsatam/agent-plugins
that referenced
this pull request
May 7, 2026
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Improves the troubleshooting-executions steering file with:
Testing
Verified changes are limited to the two steering files. No code changes.
Attached the prompts used to test this. check this comment