Repository navigation
v0.3 pushNotificationConfig/get by task id fails with Validation failed #1379
Description
What happens
A v0.3 client that sets a push config without an id and then calls tasks/pushNotificationConfig/get with only the task id gets -32603 Validation failed. In v0.3 this returned the task's config.
Why
to_core_get_task_push_notification_config_request leaves the v1.0 id unset when no config id is given, and v1.0 requires it. A config created without an id is stored under the task id (normalize_push_notification_config).
Version
main @ e12d494
Activity
rohityan commentedon Oct 27, 2026
Hi @ConnorMoss02, thanks for reporting this!
Your root-cause analysis is spot on, because un-named v0.3 push configs are stored under the task ID, querying without a config ID leaves the v1.0
idempty and fails required-field validation. The fix in #1380 defaultingv10_req.id = v10_req.task_idis the right approach.I've assigned the issue to you while we review the PR. In the meantime, you can work around this on the client side by explicitly setting
push_notification_config_idtotask_idwhen constructingGetTaskPushNotificationConfigParamsinstead of querying by task ID alone.