docs: KB refresh from Zendesk tickets (Jun 1 – Jul 31, 2026) - #2995
Merged
Conversation
Ticket-grounded KB updates mined from support tickets over a two-month window. Four corrections to existing sources and three new articles, all routed through the coverage gate to avoid duplicating the formal docs. Corrections: - Storage meter: deleting a run doesn't delete its artifacts, and GC can take up to 24 hours (~17 tickets contradicted the previous "a few hours, lifts automatically" guidance). - Missing-team login error: broaden beyond "you deleted your team" to cover accounts that never had one; clarify it isn't a real rate limit. - Sign-in troubleshooting: point "rate limit exceeded" at the real cause. - Seats: a user on two teams still uses one seat. New articles: - Bulk artifact deletion timeouts, with the batched Public API workaround. - Renaming a team or entity (not supported; the name is permanent). - Personal account to team/organization transition FAQ. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HiveMind Sessions2 sessions · 2h 34m · $60
View all sessions in HiveMind → Run |
Contributor
Knowledgebase navigation update
Generator warnings
|
Contributor
Readability impactWord-weighted Flesch-Kincaid grade change across 13 changed pages: +0.0 (unchanged). Lower Flesch-Kincaid grade and higher reading ease both mean easier to read. This check is informational and never blocks a PR. Human readability
AI agent comprehensionRated 0-3 (higher is easier for an agent to parse and act on).
Curated-docs baseline median FK grade by type: conceptual 10.5, procedural 8.8, reference 9.4. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
📚 Mintlify Preview Links✨ Added (4 total)📄 Pages (4)
📝 Changed (13 total)📄 Pages (13)
🤖 Generated automatically when Mintlify deployment succeeds |
Contributor
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Preview: https://wb-21fd5541-supportokr-073126.mintlify.site |
The `your-username-org` example generalized a naming pattern from two tickets. The transition email names each customer's actual organization, so the article doesn't need to assert the pattern. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Replace the loose "a seat represents a unique user" phrasing with the mechanism the formal docs state — seats are assigned per user at the organization level and inherited by teams — and link to the authoritative section instead of restating its details. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Verified every API call in the snippet against the wandb 0.28.1 source,
and pulled the full ticket threads to check outcomes.
Corrections:
- The agent hedged ("may be related to a known issue"); attribute the
claim rather than stating it as fact.
- Drop the "Storage Explorer" UI name, which appears nowhere in the docs
and came only from the agent reply. Point at the documented Manage
storage page instead.
Additions, all source- or ticket-verified:
- delete() on a linked artifact only unlinks it and frees no storage
(artifact.py:2345), so the script can appear to make progress it isn't.
- delete_aliases=True also removes versions carrying aliases such as
latest; say so in the warning.
- Passing an organization name instead of an entity fails with
"ValueError: Unable to parse 'ArtifactTypes' response data" (ticket
119810, agent-diagnosed) — the most likely failure for a copy-paste.
- ArtifactCollection.delete() removes a whole collection at once.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The intro described deleting a single artifact that contains many files (the agent's framing in ticket 120370), but the script deleted every artifact in the project (the customer's framing was a bulk action). The page promised one thing and delivered another. - Reframe the problem as bulk deletion, which is what the script solves: many small requests instead of one request covering the whole set. - Lead with a single-type recipe so the default is scoped, and mark the whole-project sweep as a deliberate choice. - Note that splitting the work doesn't apply to a single artifact that fails on its own, rather than implying the API avoids that timeout. Whether that timeout is client- or server-side is unverified. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The page was framed around a scenario no customer described. In the four source tickets the shared job was reclaiming storage by deleting many artifacts selectively, when the UI couldn't manage the scale: ticket 119810 wanted hundreds of `model` artifacts in one project and hit a pagination limit, not a timeout, and explicitly wanted the rest kept. - Retitle to "How do I delete many artifacts at once?" and describe the UI limits loosely rather than enumerating them. - Ship one scoped script that deletes a single artifact type. Drop the whole-project sweep, which matched no observed request and was the most destructive recipe on the page. - Quote the calls exactly as the snippet writes them, so the caveats read as descriptions of the code rather than alternatives to it. - Use [YOUR-TEAM] and [YOUR-PROJECT] placeholders. - Note that emptied collections remain listed after the script runs. Tested end to end against a live project on wandb 0.28.1: dry run listed both versions, the real run deleted them, and deleting an aliased version without `delete_aliases=True` fails with "cannot delete artifact ... due to existing alias", which is what the warning claims. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The academic/free-plan paragraph asserted that a missing Create team button "is not a bug" because "the free plan limits team creation in some cases." Nothing supports that: - No agent reply in the mined window states a plan-based limit on the number of teams. In 118950 and 118953 the agents only asked clarifying questions. - The customer in 118950 cites the opposite, that W&B advertises unlimited teams for researchers. - The only documented free-plan team limits concern seats and storage, not how many teams you can create. Replace it with the constraint that is documented — only an organization admin can create a team (platform/app/settings-page/teams.mdx:37) — and keep the support path. Telling readers a possible product problem "is not a bug" risks talking them out of reporting it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
anastasiaguspan
marked this pull request as ready for review
July 31, 2026 15:54
- Remove "or your plan doesn't let you create another team." This is the same unsupported free-plan team-cap claim removed from i-deleted-my-team-and-now-i-cant-create-a-new-one.mdx; nothing in the mined tickets or the docs establishes a per-plan limit on team count. - Stop restating the team-name rules. They already live in how-do-i-create-a-new-team-in-wandb.mdx, which step 1 links to, so repeating them here created a third copy to keep in sync. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Matt Linville <mlinville@coreweave.com>
boshwandb
reviewed
Aug 3, 2026
Retitle the team-rename FAQ to "How do I rename a team or entity?" and rework the opening so it answers a how-to instead of a yes/no question. Separate the two escalation paths that were bundled in one sentence: a team-creation permissions error goes to an organization admin, while moving a whole project goes to W&B support. Tickets 118863 and 120531 show support performing project moves, which have no self-serve path, whereas the permissions case is the org's own policy. Correct "Anyone with a W&B account can create a team" in the create-team FAQ, which contradicted both platform/app/settings-page/teams.mdx and the missing-team FAQ. Replace the duplicated procedure with links to the narrative docs, add a section for when team creation is blocked, and document that academic accounts have no team limit (older accounts may carry a low limit set at creation). Drop the unsourced team-name character rules from both team FAQs. Underscores are legal in entity names, as wandb_fc and hwinf_dcm show. Define source and link collections in the bulk-artifact-deletion FAQ and link to the registry docs for the distinction. Fold the seat-counting detail into the intro of the add-seats FAQ and refer to the AISE. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
AISE stands for "AI Solutions Engineer", not "Account Solutions Engineer". The job titles in the W&B Global Field Organization, the Pre-Sales AISE onboarding template, and the Indeed and Scribd account glossaries all expand it that way; no one holds the title "Account Solutions Engineer". Record the evidence in a source comment, and note there that the Dedicated Cloud rate-limits page still carries the unsubstantiated expansion, so a future pass can decide whether to change it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deleting a run can delete its artifacts: the W&B App prompts whether to delete the associated artifacts, and Run.delete() takes delete_artifacts. The flat claim that run deletion never removes artifacts contradicted models/runs/delete-runs.mdx, models/artifacts/delete-artifacts.mdx, the Run.delete reference, and the sibling article on recovering an artifact after deleting a run. Keep the storage explanation intact by noting that the option is opt-in and delete_artifacts defaults to False, so artifacts usually do outlive the run. Reported by boshwandb in review. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ngrayluna
previously requested changes
Aug 4, 2026
ngrayluna
left a comment
ngrayluna
left a comment
Contributor
There was a problem hiding this comment.
Thanks for updating. More feedback
|
|
||
| ## Reclaim the space | ||
|
|
||
| Deleted artifacts are soft-deleted first, then removed during garbage collection, so your storage meter doesn't drop immediately. For the timing and how to verify your usage, see [Why does the storage meter not update after deleting runs?](/support/models/articles/why-does-the-storage-meter-not-update-af) and [Delete an artifact](/models/artifacts/delete-artifacts). |
Contributor
There was a problem hiding this comment.
I'll defer to Matt w.r.t. to whether or not they ("storage meter") should get updated in this article and the other.
| import wandb | ||
|
|
||
| # Assumes you've run `wandb login` already. | ||
| entity = "[YOUR-TEAM]" # Replace with your team. |
Contributor
There was a problem hiding this comment.
TBD what the verdict s here. To unblock, we can use the current W&B doc conventions.
Contributor
Author
There was a problem hiding this comment.
okay, yes that was my plan. This syntax is what we had agreed upon as a team (it is already in the style guide skill). I mentioned to John that you wanted to reopen this discussion, so we'll probably talk about it in the next Internal Skills WG meeting. perhaps you'd like to attend as a guest to aide in this discussion?)
Regardless, yes, for this PR I think using this is appropriate for now - if we change our agreed-upon convention, a LOT of places will need to be updated, beyond just this.
Contributor
There was a problem hiding this comment.
Yup! Add me to the meeting
mdlinville
approved these changes
Aug 4, 2026
Co-authored-by: Noah Luna <15202580+ngrayluna@users.noreply.github.com>
Co-authored-by: Noah Luna <15202580+ngrayluna@users.noreply.github.com>
Co-authored-by: Noah Luna <15202580+ngrayluna@users.noreply.github.com>
Co-authored-by: Noah Luna <15202580+ngrayluna@users.noreply.github.com>
Co-authored-by: Noah Luna <15202580+ngrayluna@users.noreply.github.com>
W&B doesn't call this a "storage meter". The narrative docs use "storage usage" (managing-bucket-storage, multi_tenant_cloud, user-settings, and the billing settings UI label), so use that term instead. Covers both pages that used it: the bulk artifact deletion FAQ in this PR and the pre-existing article it links to, whose title carried the term. Reword "the meter catches up" to describe what actually happens. The article's slug still contains "storage-meter". Leaving it: the page is published and docs.json has a live redirect pointing at that slug, so renaming needs a matching redirect update. Raised by ngrayluna, terminology confirmed by mdlinville in review. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Resolve the conflict in support.mdx, which is generated: both sides bumped the W&B Models article/tag counter. main went 210 -> 211 articles, this branch went 210 -> 213 with 41 tags. The union is 214 articles and 41 tags, which matches the file count under support/models/ after the merge. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
4 participants
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.
Periodic KB refresh generated with the
wandb-kb-generatorskill. Window: 2026-06-01 → 2026-07-31 (two months, widened from the default 30 days). Mined ~1,400 tickets; ~1,090 dropped as noise/operational, leaving 14 KB-actionable concerns that went through the three gates.What changed
support/models/articles/why-does-the-storage-meter-not-update-af.mdx— correction — the old answer ("a few hours, the restriction lifts automatically") is what ~17 customers wrote in to dispute; adds the artifact/GC mechanism and a real timing figure.support/models/articles/i-deleted-my-team-and-now-i-cant-create-a-new-one.mdx— correction — the article covered this state only when the user deleted a team, but most tickets come from accounts that never had one.support/models/articles/how-can-i-resolve-login-issues-with-my-a.mdx— correction — the generic sign-in checklist never mentioned "rate limit exceeded"; adds a pointer to the real cause.support/models/articles/how-do-i-add-more-seats.mdx— correction — adds how seats are counted.support/models/articles/how-do-i-delete-many-artifacts-at-once.mdx— new — no coverage anywhere for bulk-deleting artifacts when the UI can't manage the scale.support/models/articles/can-i-rename-a-team-or-entity.mdx— new — zero coverage; the answer is "no, and the name is permanent", which also prevents the mistake.support/models/articles/what-happens-when-my-personal-account-becomes-a-team.mdx— new — zero coverage for the in-flight account restructuring.Grounding
models/artifacts/delete-artifacts.mdx.platform/hosting/iam/access-management/manage-organization.mdx:286independently confirms the mechanism: "Models seat and Weave access are defined at the organization level and inherited by the team." Folded into the existing article rather than given its own page.wandb0.28.1), changing only theartifact_typestring. The dry run listed both versions of a test artifact; the real run deleted them; a follow-up query confirmed the collection was empty.api.artifact_collections(path, type)accepts the path positionally,collection.artifacts()iterates, andversion.namerenders ascollection:alias.delete_aliases=Truewarning is load-bearing, and proven. Deleting thelatest-tagged version without the flag fails withCommError: cannot delete artifact ... due to existing alias. With the flag it succeeds. So the flag is what lets the script remove aliased versions, exactly as the warning states.modelartifacts removed from one project, hit a pagination limit rather than a timeout, and wanted everything else kept. The article now ships one scoped single-type recipe; the whole-project sweep was dropped as matching no observed request.ValueError: Unable to parse 'ArtifactTypes' response data(119810, agent-diagnosed) — the likeliest copy-paste error.delete()only unlinks and frees no storage (artifact.py:2360branches onis_link; the flag isn't forwarded).Rejected (and why)
can-i-get-an-academic-plan-as-a-studentandhow-can-i-change-my-account-from-corpora. The recurring friction is a broken link in the account-transition email (120375, 120070, 120450) — a product bug, not a content gap.platform/app/settings-page/user-settings.mdx:146already document the billing-admin blocker. Discoverability, not coverage.wandb0.27.1 distributed-training crashes (119799, 119768) — version regression, no still-open Jira.client__forking/rewind(5) — pre-settled reject from an earlier run.non-support,subscriptions__*,app__downtime__outage*,pass_to_sales,local_license_request, anduser_management___delete_user— dropped at the noise step before gating.Reviewer notes
▎ W&B is moving older personal accounts into the same team and organization structure that newer accounts already use. If you received an email about upcoming changes to your account, this change applies to you.
those are tied to the rollout being in progress. Once every old account has been converted, nobody is receiving that email anymore, and "is moving" is no longer true — it moved. The page becomes a description of something that already happened, framed as something about to happen. That's the kind of page that quietly misleads readers a year later.
i-deleted-my-team-..Replaced with the documented constraint — only an organization admin can create a team (platform/app/settings-page/teams.mdx:37`) — keeping the support path. Flagging for a reviewer who knows the plan logic: if a genuine per-plan team cap does exist, it belongs in the formal docs, not reinstated here.-note: agent claims The team-name rules (globally unique, lowercase, no spaces) are asserted only in KB articles, not in the formal docs. might want to consider adding that somewhere official.
🤖 Generated with Claude Code