-
Notifications
You must be signed in to change notification settings - Fork 54
docs: KB refresh from Zendesk tickets (Jun 1 – Jul 31, 2026) #2995
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
d6ba9c8
137e6ca
e7fd2dc
52fe2c5
c219430
032560d
535d92f
d893f10
affb04f
aa783db
3481898
1b5339b
089831b
7ef23ba
0c62cbf
a855c98
8383509
f2e8731
0ecaf40
5a1197d
7786032
d2660d3
e165cec
d62a719
b14b27e
7849a93
7db5e3a
03eb9a6
8e7dfe8
48c62e7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| --- | ||
| title: "How do I delete many artifacts at once?" | ||
| keywords: ["Artifacts", "Storage", "Python API"] | ||
| --- | ||
|
|
||
| When you need to delete many artifact versions, such as to reduce storage usage, use the [W&B Public API](/models/ref/python/public-api/api) instead of the W&B App. Bulk deletions in the App can time out with a `context deadline exceeded` error, and the artifact list is not designed for deleting hundreds of versions. | ||
|
|
||
| The following script deletes all artifact versions of a specified type in a project. | ||
|
|
||
| Replace the `[YOUR-TEAM]` and `[YOUR-PROJECT]` placeholders with your own values. Use your team or username for `[YOUR-TEAM]`, not your organization name. | ||
|
|
||
| <Warning> | ||
| Artifact deletion is destructive. When deleting source artifact versions, W&B deletes the artifact and its files. Passing `delete_aliases=True` enables deletion of versions with aliases such as `latest`, and removes those aliases. | ||
|
|
||
| Use `DRY_RUN = True` first, review the printed artifact names, and only then set DRY_RUN = False. | ||
| </Warning> | ||
|
|
||
| ```python | ||
| import wandb | ||
|
|
||
| # Assumes you've run `wandb login` already. | ||
| entity = "[YOUR-TEAM]" # Replace with your team. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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?)
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yup! Add me to the meeting |
||
| project = "[YOUR-PROJECT]" # Replace with your project. | ||
| artifact_type = "model" # Replace with the artifact type to delete. | ||
|
|
||
| # Keep this set to True until you review the versions to delete. | ||
| DRY_RUN = True | ||
|
|
||
| api = wandb.Api() | ||
|
|
||
| for collection in api.artifact_collections(f"{entity}/{project}", artifact_type): | ||
| for version in collection.artifacts(): | ||
| if DRY_RUN: | ||
| print(f"[dry-run] would delete {version.name}") | ||
| else: | ||
| print(f"Deleting {version.name}") | ||
| version.delete(delete_aliases=True) | ||
| ``` | ||
|
|
||
| The script deletes artifact versions, not collections. An emptied collection still appears in the project's **Artifacts** tab. | ||
|
|
||
| `wandb.Api.artifact_collections()` returns both source collections and link collections: | ||
|
|
||
| - A source collection contains artifact versions logged to runs in the project. | ||
| - A link collection contains references to artifact versions linked to another collection, such as a collection in a registry. | ||
|
|
||
| For more information, see [Link an artifact version to a collection](/models/registry/link_version). | ||
|
|
||
| When a version comes from a link collection, `version.delete(delete_aliases=True)` removes only the link. The source artifact and its files stay where they are, so that version frees no storage. | ||
|
|
||
| ## Reclaim the space | ||
|
|
||
| Deleted artifacts are soft-deleted first, then removed during garbage collection, so your storage usage doesn't drop immediately. For the timing and how to verify your usage, see [Why doesn't my storage usage update after deleting runs?](/support/models/articles/why-does-the-storage-meter-not-update-af) and [Delete an artifact](/models/artifacts/delete-artifacts). | ||
|
|
||
| --- | ||
|
|
||
| {/* AUTO-GENERATED: tab badges */} | ||
| <Badge stroke shape="pill" color="orange" size="md">[Artifacts](/support/models/tags/artifacts)</Badge><Badge stroke shape="pill" color="orange" size="md">[Storage](/support/models/tags/storage)</Badge><Badge stroke shape="pill" color="orange" size="md">[Python API](/support/models/tags/python-api)</Badge> | ||
| {/* END AUTO-GENERATED: tab badges */} | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| --- | ||
| title: "How do I rename a team or entity?" | ||
| keywords: ["Teams", "Team Management", "Org Management"] | ||
| --- | ||
|
|
||
| W&B doesn't support renaming a team or entity. A team's name is set when you create the team and can't be changed afterward. Instead, create a new team with the name and members you want, then move your work into it: | ||
|
|
||
| 1. [Create the new team](/platform/hosting/iam/access-management/manage-organization#create-a-team). If you get a permissions error, your organization restricts who can create teams. Ask an organization admin to create the team for you. | ||
| 2. Move your projects or runs into the new team. You can move runs between teams in W&B, but logged artifacts don't move automatically. | ||
| 3. To move an entire project, [contact support](mailto:support@wandb.com) with the source team, the destination team, and the projects to move. Support schedules the move during a window when nothing is actively logging to either team. | ||
|
|
||
| <Note> | ||
| A team's storage location is also fixed at creation. Configure a team's storage location when you create the team. See [Secure storage connector](/platform/hosting/data-security/secure-storage-connector). | ||
| </Note> | ||
|
|
||
| --- | ||
|
|
||
| {/* AUTO-GENERATED: tab badges */} | ||
| <Badge stroke shape="pill" color="orange" size="md">[Teams](/support/models/tags/teams)</Badge><Badge stroke shape="pill" color="orange" size="md">[Team Management](/support/models/tags/team-management)</Badge><Badge stroke shape="pill" color="orange" size="md">[Org Management](/support/models/tags/org-management)</Badge> | ||
| {/* END AUTO-GENERATED: tab badges */} |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| --- | ||
| title: "What happens when my personal account becomes a team and organization?" | ||
| keywords: ["Org Management", "Team Management", "Academic"] | ||
| --- | ||
|
|
||
| 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. | ||
|
|
||
| You don't need to take any action. This is a platform-wide change, not something specific to your account. | ||
|
|
||
| ## What changes | ||
|
|
||
| The change affects your account structure as follows: | ||
|
|
||
| - Your personal account becomes a team attached to a new organization named after your username. You are an admin of that organization. | ||
| - Your data stays where it is. Projects, runs, artifacts, and existing links continue to work. | ||
| - Organizations and teams you already belong to are separate and aren't affected. | ||
| - The new organization starts with a free 30-day Pro trial. When the trial ends, the organization moves to the Free plan unless you upgrade. | ||
|
|
||
| ## If you have an academic plan | ||
|
|
||
| Your existing organization keeps its academic subscription. However, the new organization created for your personal account is a separate organization, so it needs its own academic application. You can apply for it with the same email address on the [W&B academic application page](https://wandb.ai/academic_application). | ||
|
|
||
| For how academic plans work, see [Can I get an academic plan as a student?](/support/models/articles/can-i-get-an-academic-plan-as-a-student). | ||
|
|
||
| ## If you can't find your runs after the change | ||
|
|
||
| Your data isn't deleted as part of this change. If projects or runs appear to be missing, or you're blocked from viewing them, [contact support](mailto:support@wandb.com) with your username and organization name so support can check your account configuration. | ||
|
|
||
| --- | ||
|
|
||
| {/* AUTO-GENERATED: tab badges */} | ||
| <Badge stroke shape="pill" color="orange" size="md">[Org Management](/support/models/tags/org-management)</Badge><Badge stroke shape="pill" color="orange" size="md">[Team Management](/support/models/tags/team-management)</Badge><Badge stroke shape="pill" color="orange" size="md">[Academic](/support/models/tags/academic)</Badge> | ||
| {/* END AUTO-GENERATED: tab badges */} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh man, the target page does not have an ideal name or slug. No issue with the edit to this file, though.