Performance & limits
Foundation runs on Atlassian Forge, which imposes a handful of hard platform limits. A lens that feels slow or a Sync Agent that times out is almost always bumping into one of them. This page lists the limits, the symptoms, and the workaround.
Known limits
Section titled “Known limits”- 1,000 issues per lens (MVP). Beyond this, scroll and edit performance degrade. Split large portfolios into focused lenses.
- Jira API rate limit. Foundation is on Tier 2 (per-tenant). Most sites have 100,000–500,000 points per hour. Large Sync Agent runs can still spike the budget briefly.
- 25-second standard function timeout. Short resolver calls complete well inside this. Heavier operations are handed off to async events.
- 15-minute async event timeout. Bulk Sync Agent runs and imports run as async jobs inside this budget.
- 5 MB frontend response payload. The grid never hits this, but exports of very large lenses might trim.
- 150 Forge SQL writes per second. Imports are chunked to stay under this.
- BROWSE cache: 15 minutes per user. Permission changes propagate on that cadence.
Symptom: grid feels sluggish
Section titled “Symptom: grid feels sluggish”- Check the lens’s issue count in the Inspector’s Data section.
- If it’s near or over 1,000, split the lens by time window, team, or fixVersion.
- If it’s well under 1,000 but still slow, try a tighter density mode — Compact or Super-compact — and see if it’s a rendering issue rather than a data issue.
- Collapse parents you don’t need expanded. The grid renders everything visible.
Symptom: Sync Agent times out
Section titled “Symptom: Sync Agent times out”- Open the Sync Agents panel and check the error.
- If the message mentions timeout, the JQL is returning too many issues for one run.
- Narrow the JQL — add a date range, a project filter, or a status filter.
- Split one huge agent into several smaller ones targeting different slices.
Symptom: rate-limit message
Section titled “Symptom: rate-limit message”- Ask your admin to check the Monitoring dashboard. Look at API point usage for the last hour.
- Spikes usually trace to one big Sync Agent run or a bulk import.
- Stagger large imports or schedule heavy agents during off-peak hours.
- If your site is regularly pressed against the budget, consider whether a few JQL agents can be scoped tighter.
Symptom: export truncated
Section titled “Symptom: export truncated”If a CSV export seems short:
- Confirm no quick filter or collapsed parent is masking rows.
- Expand all parents before exporting (the export respects visible tree order).
- For very large exports, Foundation may split into chunks — check your browser’s downloads.
- Keep lenses focused. A lens should answer one question: “What’s the state of Q2 platform work?” is better than “Everything the platform org has ever touched.”
- Use saved views instead of separate lenses when you only need different column sets on the same data.
- Let Sync Agents run in the background — refresh a large lens once an hour, not every minute.