Debugging

Use this page for quick verification and response-code triage when an A2A integration is not working as expected.

Quick verification

Check the Agent Card

1
2
curl -s https://a2a.atlassian.com/.well-known/agent.json | jq .

Use this to verify discovery and inspect the current url, securitySchemes, and skills values.

Check OAuth metadata

Fetch the protected-resource metadata endpoint:

1
2
curl -s https://a2a.atlassian.com/.well-known/oauth-protected-resource/v1/rovo | jq .

The Agent Card also contains the OAuth security scheme:

1
2
curl -s https://a2a.atlassian.com/.well-known/agent.json | jq '.securitySchemes'

Send a minimal request

1
2
curl -sS -N --max-time 240 \
  -X POST https://a2a.atlassian.com/v1/rovo \
  -H "Content-Type: application/json" \
  -H "Accept: text/event-stream" \
  -H "Authorization: Bearer <your_access_token>" \
  -d '{
    "jsonrpc": "2.0",
    "id": "11111111-1111-4111-8111-111111111111",
    "method": "message/stream",
    "params": {
      "message": {
        "kind": "message",
        "messageId": "22222222-2222-4222-8222-222222222222",
        "role": "user",
        "parts": [{ "kind": "text", "text": "Hello, Rovo" }]
      }
    }
  }'

Common response codes

HTTP status	Meaning	Typical next check
`200`	Gateway returned a task response	Inspect `result.status.state` and `result.status.message.parts`
`400`	JSON-RPC error from the gateway	Validate request shape and method support
`401`	Authentication rejected before execution	Check the bearer token and scopes
`403`	Organization access blocked	Confirm A2A is enabled for the organization
`404`	Endpoint unavailable	Confirm the path and rollout status
`500`	Request exceeded the edge response limit	Sent with `message/send` and ran past roughly 30 seconds. Use `message/stream`

Common JSON-RPC errors

The gateway returns these codes itself:

Error code	Meaning
`-32600`	Invalid JSON-RPC request structure
`-32601`	Unknown method
`-32603`	Internal error while invoking the downstream Rovo service
`-32006`	The downstream Rovo service returned an unusable response
`-32007`	A2A is not enabled for the organization
`-32008`	The organization could not be resolved from the access token
`-32401`	The access token is missing or has expired

The gateway also forwards JSON-RPC errors from the downstream Rovo service unchanged, so you may receive a code that is not in this table. Treat any unrecognized code as a failed request and surface its message to the caller.

Diagnosing a specific failure

These checks confirm the endpoints respond. Once you have a specific symptom, Troubleshooting is the symptom index: auth failures, -32007, invalid requests, timeouts, and failed task results.

Next steps

End-to-end testing — Run authenticated checks against the live endpoints.
Troubleshooting — Detailed fixes for common failures.
Authentication — Review OAuth 2.0, scopes, and org enablement.
Architecture — Confirm the current request flow and method support.