docs: consolidate concurrency usage chart documentation (replaces #710, #725) - #738
Draft
jordanc-relevanceai wants to merge 1 commit into
Draft
docs: consolidate concurrency usage chart documentation (replaces #710, #725)#738jordanc-relevanceai wants to merge 1 commit into
jordanc-relevanceai wants to merge 1 commit into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This was referenced Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Consolidates the two open PRs that rewrote the same Concurrency usage section into one change. Branched from
main.enterprise/analytics.mdx— stacked bar chart description, Running/Queued bands, when queued tasks appear, per-project breakdown as a manager-only toggle, tooltip layout, link to System Quotas.admin/subscriptions/plans.mdx— corrects "time-series area chart" to "stacked bar chart", describes the two bands, and cross-links the per-project breakdown.Replaces these PRs (now closed)
plans.mdxcorrectionThese two directly contradicted each other on the same paragraphs, so they could not both merge.
The conflict, and how it was resolved
#710 said the per-project breakdown is a toggle visible to organization managers. #725 said "The chart always shows a breakdown by project." #710 is right.
In
relevance-api-node, the per-project view requires both organization-management permission and theanalytics-agent-concurrency-project-breakdownflag — the code comment reads "Per-project breakdown requires both org-management permission and the flag", and without them "the whole org renders as a single band". The flag is at 100% rollout, so the flag half is no longer a reach problem, but the permission gate is real and permanent. Documented as a manager-only toggle.Other correction
Band colours. #725 described the running band as blue. The running ramp starts at
#6858FF— brand indigo/purple — so it is described as purple here. The queued band is genuinely red (#912018–#FDA29Bramp), and the chart's own help text says "Red shows tasks queued over the limit."Verified as accurate and kept
/admin/system-limits#concurrent-tasksresolves — that page has a## Concurrent Tasksheading.analytics-agent-concurrency-queue-depth, also at 100% rollout, so it is safe to document.Test plan
/enterprise/analytics#per-project-breakdownanchor resolves fromplans.mdx/admin/system-limits#concurrent-tasksanchor resolves