Skip to content

[aw] Issue Monster hit engine rate limit (HTTP 429) #65909

Description

@github-actions

Workflow Failure

Workflow: Issue Monster
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/37347574517

Warning

Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

Reasons:

  • infrastructure_error

    All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

Failure Diagnostics

Failing step: Execute Pi CLI

Warning

Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

This signal was detected from engine runtime logs/OTLP telemetry.

What to do next

  • Retry the workflow after a short delay.
  • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/gh-aw/actions/runs/37347574517
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Issue Monster · ◷

  • expires on Oct 6, 2026, 5:26 AM UTC

Activity

  1. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37350576925 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  2. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37356255349 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  3. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37359027182 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  4. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37375198776 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  5. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37377749569 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  6. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37381831850 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  7. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37384072534 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  8. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37387798938 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  9. github-actions commented on Oct 5, 2026

    @github-actions
    ContributorAuthor

    Agent job 37389872115 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  10. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    Agent job 37396681496 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  11. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    Agent job 37400018463 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  12. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    Agent job 37404652092 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  13. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    Agent job 37406289709 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  14. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    Agent job 37409019168 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  15. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    Agent job 37410834267 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  16. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    Agent job 37413732093 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  17. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    Agent job 37415446243 failed.

    Warning

    Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

    Reasons:

    • infrastructure_error

      All 1 Pi provider requests failed before safe outputs were emitted. Last provider failure: message="aw-gateway API error (400): {"message":"Unsupported Responses custom tool 'codemode'. Only 'apply_patch' is supported through the Copilot compatibility adapter.","type":"invalid_request_error","code":"unsupported_custom_tool"}".

    This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

    Failure Diagnostics

    Failing step: Execute Pi CLI

    Warning

    Engine Rate Limited (HTTP 429): The pi engine hit provider rate limits and could not complete this run.

    This signal was detected from engine runtime logs/OTLP telemetry.

    What to do next

    • Retry the workflow after a short delay.
    • If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

    Generated from Issue Monster · ◷

  18. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-06T05:26:45.350Z.

    Closed by Workflow

  19. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-06T05:26:45.350Z.

    Closed by Workflow

  20. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-06T05:26:45.350Z.

    Closed by Workflow

  21. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-06T05:26:45.350Z.

    Closed by Workflow

  22. github-actions commented on Oct 6, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-06T05:26:45.350Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions