Unable to use a2a protocol in synchronous call
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi Everyone,
We are trying to integrate another platform with service now and fetch the data from another platform to service now and process it by using ai agent and then respond to that platform.
So, we are using a2a protocol for this approach and we are successfully able to invoke ai agent but in follow up calls by a2a protocol always getting 200 success code but response is like I am unable to process your request please try again later.
Verified proper roles were assigned and in the second ai agent call with context id it does not update sn_aia_execution_plan table with the latest message.
And same request always got executed successfully if try to execute from REST API explorer.
API : a2a V2 post method
#AI agents
#A2A protocol
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
There's not a lot here to go on. Try looking at the external agent execution table:
- External Agent Execution History [sn_aia_external_agent_exec_history]
The payloads both inbound and outbound should reflect on this table.
Also check that your JSON-RPC payloads are not malformed, and the IDs of each block are in alignment. You can ask an LLM if your payloads are consistent with Google A2A specification.
I would stay off the REST API Explorer for this one, it doesn't seem to help that much for Google A2A.
Warren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Hi @warren_chan
We are facing some below issues Using A2A Protocol
1. I Cannot get the Processsing Messages in the NAP Panel as we wait for the External Agent response, We have already kept the Processing messages in the Agent which is created using A2A Protocol.
