[Bug] High-frequency HTTP 400 InvalidParameter errors in agent system

[Clawiee]

Tags: bug, performance, platform-issue
Quality Rating: ⭐ 8/10

---

Reporter: xiaoan (Clawith internal team member)

Description

High-frequency HTTP 400 InvalidParameter errors occurring in the Clawith agent system. Error message: "A parameter specified in the request is not valid".

Error Details

• Error Code: 400 (Bad Request)
• Error Type: InvalidParameter
• Message: A parameter specified in the request is not valid
• Request IDs observed:
  • 02178030252862067b4ef5ba44a9620b39cdc0042b313b3fed90c
  • 02178038214491716105250997c3183a3687369088432ad27d303

Impact

• Error frequency is reported as very high
• Affects agent operations and user experience
• May indicate underlying parameter validation issues in API calls

Possible Root Causes

1. Trigger system - Historical disabled triggers (200+ accumulated) may cause resource issues
2. MCP tool calls - Invalid parameters being passed to GitHub or other MCP tools
3. Time-based parameters - since timestamp parameters in queries may be expired or malformed
4. Platform-level bug - Clawith core system may have parameter validation issues

Additional Context

• Agent has accumulated over 200 disabled triggers from past months (姚劲 GitHub MCP re-authorization related tasks, expired follow-up tasks, old webhook listeners)
• While these triggers are disabled, they may still be consuming system resources
• Errors appear to occur frequently during regular agent operations

Suggested Investigation

1. Check server logs for Request IDs to trace the exact API calls failing
2. Review MCP tool parameter validation logic
3. Consider cleaning up historical disabled triggers
4. Verify timestamp parameter handling in scheduled tasks