Atlassian is throttling us, finding dispatch will stall. Back off bulk-create and warn the merchant.
At a glance
Rate-Limit Exhausted is a nerve centre metric tracked from Jira data. It surfaces operational signal at the nerve centre layer so merchants can spot regressions, opportunities, and structural patterns in their store performance. The card pairs with sibling metrics in the Nerve Centre category to build a complete diagnostic picture; cross-reference the related cards listed below for context.
| What it counts | Rate-Limit Exhausted as exposed by the Jira integration. The metric is computed from the latest available data and refreshed on the standard data refresh. |
| Sample type | Backend API data from Jira, refreshed on the standard data refresh. |
| Why it matters | The metric appears in the Nerve Centre category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities. |
| Reading the value | Compare the current period to the prior period to identify direction. Cross-reference siblings for the full diagnostic picture. |
| Currency | number |
| Time window | RT |
| Alert trigger | 429s in last 1h OR headroom <5% |
| Sentiment key | jira_alert_rate_limit_exhausted |
| Roles | owner, operations |
Calculation
Calculated automatically from your Jira data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A representative reading of Rate-Limit Exhausted for a typical merchant on Jira. The card reports the current period value alongside a comparison against the previous period. Direction matters: rising values may be healthy or concerning depending on the underlying metric. Cross-reference the siblings below to triangulate cause when the value moves outside expected range. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
jira_alert_abandoned_findings_burst | Nerve Centre sibling: Abandoned-Findings Burst. |
jira_alert_token_expiry_imminent | Nerve Centre sibling: Atlassian Token Expiry Imminent. |
jira_alert_unassigned_critical_burst | Nerve Centre sibling: Unassigned Critical Tickets. |
jira_active_sprint_progress | Sprint sibling: Active Sprint Progress. |
jira_rate_limit_headroom | Atlassian Operations sibling: API Rate-Limit Headroom. |
Reconciling against the vendor’s own dashboard
Where to look in Jira’s own dashboard: The Jira dashboard surfaces this metric (or its components) under the relevant report section. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses 30-day rolling by default; vendor dashboards may use calendar periods. | Variable | Match the period range. |
| Time zone. Vendor uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (channel, B2B, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |