# MCP tool calls show "Unable to reach JIRA" while in-flight even when they succeed

**URL:** <https://community.developer.atlassian.com/t/mcp-tool-calls-show-unable-to-reach-jira-while-in-flight-even-when-they-succeed/102512>\
**Category:** Rovo Dev\
**Tags:** atlassian-mcp\
**Created:** [September 4, 2026, 3:38pm UTC](https://community.developer.atlassian.com/t/mcp-tool-calls-show-unable-to-reach-jira-while-in-flight-even-when-they-succeed/102512 "2026-09-04T15:38:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BetteBott](https://avatars.discourse-cdn.com/v4/letter/b/f9ae1b/32.png) [@BetteBott](https://community.developer.atlassian.com/u/BetteBott)\
**Post date:** [September 4, 2026, 3:38pm UTC](https://community.developer.atlassian.com/t/mcp-tool-calls-show-unable-to-reach-jira-while-in-flight-even-when-they-succeed/102512/1 "2026-09-04T15:38:25Z")

</div>

When firing multiple `GetTransitionsForJiraIssue` (or similar) tool calls in parallel through the Atlassian MCP server, each pending call displays “Unable to reach Jira” as its status label while it is still in flight. Once the calls complete, the results are correct and the summary confirms success.

The label “Unable to reach Jira” implies a connection failure, which is alarming and misleading — especially when batching calls. A neutral loading state like “Calling Jira…” or a simple spinner would be far less confusing.

**Steps to reproduce:**

1. Fire multiple MCP tool calls in parallel (e.g. transition 7 issues at once)
2. Observe the in-flight status label for each call

**Expected:** A neutral loading/pending indicator  
**Actual:** “Unable to reach Jira” shown while calls are pending

 ![image](https://global.discourse-cdn.com/atlassiandeveloper/original/3X/6/4/64a48fa05c9f7a9735be1dc5ab4959f6848da98b.png)