Last updated: October 18, 2026

StatusPulse — Troubleshooting

The app shows a blank page or a loading placeholder that never finishes

Almost always a DNS or network problem on your side, not the app.

Forge apps — every app on the Atlassian Marketplace built on Forge, not just this one — load their interface from *.cdn.prod.atlassian-dev.net. If your network cannot resolve or reach that domain, Jira draws the frame and then waits for an app that never loads. You get an empty panel with no error message, which is a genuinely unhelpful failure and not one an app author can improve.

How to confirm it in ten seconds. In a terminal:

nslookup probe.cdn.prod.atlassian-dev.net

If that returns an address, DNS is fine and the problem is elsewhere. If it returns nothing or NXDOMAIN, that is your answer.

How to fix it, in order of likelihood:

Your router or ISP DNS does not resolve the domain. Point the machine at a public resolver. On macOS:
```
sudo networksetup -setdnsservers Wi-Fi 8.8.8.8 1.1.1.1
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
```
On Windows, set DNS to 8.8.8.8 and 1.1.1.1 in the adapter's IPv4 properties.
A corporate firewall or proxy. Ask IT to allow *.cdn.prod.atlassian-dev.net. Atlassian documents this domain as required for Forge apps to run. It is also worth excluding *.atlassian.com, *.atlassian.net and *.atl-paas.net from TLS inspection.
A browser extension. Ad blockers and privacy extensions sometimes block third-party frames. Pause them for your Jira site and reload.
A DNS-filtering service such as a Pi-hole, NextDNS or OpenDNS with an aggressive blocklist.

How to be sure it is not the app: open Chrome DevTools, go to Console, and use the frame selector at the top left, which normally reads top. If the app's frame shows as chromewebdata, that is Chrome's error page — the frame never loaded, so no app code ever ran. Nothing an app author changes can affect that.

“Jira rejected the search”

The JQL is not valid, or you cannot see the projects it names. The message includes Jira's own explanation, which is usually more precise than anything we could add. Try the same query in Jira's issue search first.

“Showing the first 200 issues”

A report is capped at 200 issues so it cannot time out halfway and show you nothing. Narrow the query by project, date range or issue type. Two accurate reports beat one truncated one.

Some issues are marked “partial history”

Jira caps how much changelog it returns alongside a search, and it returns the most recent entries first. So for a long-lived, heavily-edited issue what StatusPulse cannot see is that issue's early life.

StatusPulse measures those issues from the oldest entry Jira did send, and charges the unknown period to no status. Their totals are a lower bound — real time in status is at least that much, possibly more — and never an over-count. This is surfaced rather than hidden so you know which rows to treat carefully.

A row says “Done” but the time next to it looks enormous

It should not, any more. Before this was fixed, an issue with a truncated changelog had its whole unmeasured early life charged to whichever status sat at the edge of what Jira returned. If you see a number that cannot be right, send us the issue key — the calculation is deterministic, so one example reproduces it exactly.

The StatusPulse icon is missing from the gadget picker

Atlassian requires a dashboard gadget's icon to be given as a web address, so it is served from shaileshchaudhari.vercel.app/statuspulse/icon-144.png rather than from inside the app. If your network blocks that address the gadget still works perfectly — only its picture is missing. Nothing about your Jira is sent when the browser fetches it.

The numbers look too small

Check the Measure setting. On Working hours a ticket raised on Friday evening and resolved Monday morning shows a few hours, not three days, because that is what actually happened. If your team genuinely works around the clock, switch to Calendar time.

Then check your holidays list. A holiday is excluded entirely, so a ticket sitting across Diwali or Christmas will show less time than the calendar suggests.

The numbers look too big

Check the working day. A day defined as 00:00–23:59 counts everything. Check the working week too: “No weekend — all seven days” does what it says.

Status names are missing or the report is empty for a non-English Jira

It should not be. StatusPulse matches status changes on Jira's stable internal field identifier as well as the visible field name, specifically so localised instances work. If you see this, it is a bug we want to hear about, with your site language.

A status we renamed appears twice in the report

It should not. Jira records the name a status had at the time of each transition, so a rename leaves one status wearing two names in the history — and StatusPulse rewrites every recorded name to the name that status has today, using the identifiers Jira sends alongside the names.

There are two cases where it can still happen, and the report says so in both:

StatusPulse could not read your site's status list. You will see the warning “Could not read Jira's status list, so cycle time is not shown and a status renamed at some point may appear as two rows.” Cycle time will be missing too. It is a permissions or availability problem on the /rest/api/3/status endpoint.
The status was deleted, not renamed. A status Jira no longer knows about keeps the name your history recorded, because the alternative is losing the row entirely.

If neither applies, tell us the two names you are seeing — that is a bug.

The gadget shows different numbers from the page

For one person, it should not be able to: the gadget calls the same code with the same saved settings. If they disagree, the page's settings were changed and not saved — press Save these settings on the page and reload the dashboard.

Two people looking at the same dashboard is a different question, and the answer is by design. Settings are saved against your Atlassian account, not against the site or the dashboard, so each viewer's gadget runs their own saved JQL and working calendar. On a shared dashboard that means two people can genuinely see two different reports, and neither is wrong.

It works that way because a shared setting would be wrong for somebody: two people on one Jira often work different hours, and quietly measuring one of them against the other's calendar is exactly the failure this app exists to avoid. If your team needs one agreed number on a wall display, agree the query and have everyone save the same one — or tell us. A gadget with its own configuration is a considered feature we have not built, not an oversight.

Reporting something we have not covered

Tell us the JQL, the settings you used, and roughly what you expected. If you can include an issue key where the number looks wrong, that is the fastest possible bug report: the calculation is deterministic, so one example is usually enough to reproduce it exactly. Use the StatusPulse support desk.