Skip to content

[cli-tools-test] Improve error messaging for non-existent workflow in logs command #15215

@github-actions

Description

@github-actions

Problem Description

When querying logs for a workflow that doesn't exist, the MCP server returns a generic MCP error instead of a user-friendly error message.

Command/Tool

  • Tool: logs
  • Command: agenticworkflows-logs with workflow_name: "nonexistent-workflow-xyz-12345"

Steps to Reproduce

  1. Use the agentic-workflows MCP server logs tool
  2. Provide a workflow name that doesn't exist (e.g., "nonexistent-workflow-xyz-12345")
  3. Observe the error response

Expected Behavior

One of:

  • Empty result set with summary indicating 0 runs found
  • Clear error message: "Workflow 'nonexistent-workflow-xyz-12345' not found. Available workflows: ..."
  • Helpful suggestion to check workflow name spelling or use list command

Actual Behavior

Generic MCP error:

McpError: MCP error -32603: calling "tools/call": failed to download workflow logs: exit status 1

Environment

  • Repository: github/gh-aw
  • Run ID: 21958431840
  • Date: 2026-02-12
  • Testing Context: Daily CLI Tools Exploratory Testing

Impact

  • Severity: Medium
  • Frequency: Every time an invalid workflow name is provided
  • Workaround: Users must manually verify workflow names using the list command first

Recommended Fix

Add validation layer in the logs command that:

  1. Pre-validates workflow name against known workflows
  2. Returns structured error with helpful context
  3. Suggests corrections (fuzzy matching) or lists available workflows

Example improved error:

{
  "error": "workflow_not_found",
  "message": "Workflow 'nonexistent-workflow-xyz-12345' not found",
  "suggestions": ["Did you mean: test-workflow, test-dispatcher-workflow?"],
  "help": "Run 'gh aw status' to see all available workflows"
}

Additional Context

This issue was discovered during comprehensive exploratory testing of the agentic-workflows MCP server. The same pattern affects the audit command when provided with invalid run IDs (see related issue).

AI generated by Daily CLI Tools Exploratory Tester

  • expires on Feb 19, 2026, 6:13 PM UTC

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions