claude-code - 💡(How to fix) Fix /schedule: 'Run now' fails on both CLI (RemoteTrigger run action) and web UI [1 comments, 2 participants]

{"type":"error","error":{"type":"invalid_request_error","message":"trigger_id: Extra inputs are not permitted"}} The validation error message trigger_id: Extra inputs are not permitted suggests the request body is being validated with a strict (extra=forbid) schema and trigger_id — which belongs only in the URL path POST /v1/code/triggers/{trigger_id}/run — is being inserted into the body as well, presumably by a shared serializer also used by get/update. Same root cause likely behind the web UI's silent toast.

TL;DR

Remove the trigger_id from the request body when calling the RemoteTrigger tool or modify the web UI's Run now button to not include it.

Guidance

• Verify that the trigger_id is being passed correctly in the URL path for the RemoteTrigger tool, and not included in the request body.
• Check the shared serializer used by get/update and run actions to ensure it's not inserting the trigger_id into the body.
• Test the RemoteTrigger tool with an empty request body to confirm that the issue is resolved.
• Consider modifying the web UI's Run now button to use the same corrected request format as the RemoteTrigger tool.

Example

No code snippet is provided as the issue is related to the request format and not a specific code implementation.

Notes

The provided workaround of waiting for the next cron fire is a temporary solution and does not address the root cause of the issue. The suggested fix aims to resolve the problem by correcting the request format.

Recommendation

Apply workaround: Remove the trigger_id from the request body, as it is likely causing the validation error and preventing the manual run from working. This change should allow the RemoteTrigger tool and web UI's Run now button to function correctly.