You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: there is no push notifications after every updates of task while sendMessage is called by the client #617
according to the A2A protocol version 1.0.0, section 3.5. Task Update Delivery Mechanisms: The A2A protocol provides three complementary mechanisms for clients to receive updates about task progress and completion. Push Notifications (WebHooks) is one of the mechanisms, it defines that Agent sends HTTP POST requests to client-registered endpoints when task state changes.
But at the code implements of A2A java, the notification is not send every updates of the task, there is the code at DefaultRequestHandler.java: line 506
// Send push notification after initial return (for both blocking and non-blocking)
pushNotificationCallback.run();
it only send push notification after initial return.
plz fix it
@zoujie-ee I think #611 should fix it. Please look in the new MainEventBusProcessor which is the central place now for updating tasks. Let me know if you have any concerns.
Activity
kabir commentedon Jan 30, 2026
Hi, I am currently reworking where the push notifications are sent from. Although, what is being sent is out out of scope for what I am working on.
But I wonder if this issue is a duplicate of #490?
zoujie-ee commentedon Jan 31, 2026
may not the same one, issue 490 is focus on what to send, while in my issue, the problem is when to send the notifications
kabir commentedon Feb 4, 2026
@zoujie-ee I think #611 should fix it. Please look in the new MainEventBusProcessor which is the central place now for updating tasks. Let me know if you have any concerns.
I'll move on to #490 next
kabir commentedon Feb 12, 2026
@zoujie-ee I believe this has been done in 1.0.0.Alpha2. If not, feel free to reopen