Troubleshooting

I cannot find an artifact

1. Check the active team.
2. Clear search, type, owner, and workspace filters.
3. Check the workspace that contains the artifact and confirm you are a member.
4. If an agent created it, ask the agent to run anima list across all reachable workspaces. These are the workspaces it has permission to access. It can also filter with the intended workspace ID.

A team can contain workspaces you cannot reach. A link alone does not grant access. See Request access to a private artifact.

A private link will not open

If signed out, sign in with the intended account. If signed in, verify the active account and team, then ask a workspace manager for access. Pending invitations must be accepted before they provide visibility. The access error does not reveal hidden owners, recipients, workspace names, or artifact existence.

My Markdown edit did not persist

Wait for the autosave indicator. If it reports an interruption, keep the page open and retry after the connection recovers. Save or Command-S creates an explicit history checkpoint, but routine edits do not require manual saving.

After reconnecting, compare the current document and History before reapplying text. Restore an earlier version if an unwanted result was saved. See Edit a Markdown artifact.

Two people edited at once

Live collaboration normally merges updates and shows presence or remote selections where available. If an offline reconnect or conflict produces the wrong result, inspect History, restore the desired version, and reapply the smaller change. Reloading before every edit is not a normal requirement.

Folder or ZIP import failed

Folder and ZIP import is live. Check:

• one folder or archive was selected;
• total size is at most 50 MiB;
• there are at most 1,000 files;
• paths and ZIP structure are valid;
• dependencies and build output are excluded;
• an app has an entry point, or a Markdown import has .md files; and
• the team has artifact capacity.

Correct source errors and create a new import. See Import a folder or ZIP.

URL or Figma import was refused

Confirm the source and authorization. On Free, both methods share five successful imports total. An exhausted allowance opens or relays an upgrade path; retries and deleting old imports do not restore it.

Publishing failed or looks stale

Verify that the artifact type and plan support publishing, that an agent has the publish capability, and that a human explicitly requested publication. Artifact edits do not automatically update an already published site; publish the current state to update it. Unpublish removes the public site without deleting the artifact. See Publish to a public URL.

A review comment or notification opens nothing

The destination may have moved, been deleted, or become inaccessible. Check workspace access. For stale anchors, open the artifact and locate the surrounding content manually. Agents can use anima review list, reply, and resolve only for comments they can reach.

An agent created work in the wrong workspace

Run anima workspaces and identify the correct workspace ID. New creation and duplication should use --workspace <id>. With several writable workspaces there is no default. Move the artifact when current permissions allow it, or duplicate into the intended destination when a separate copy is acceptable.

An agent invite was created but nothing happened

Creating an invite does not connect an agent. Copy the one-time link and deliver it. The agent must redeem it before appearing in agent administration.

An agent stopped working

• Workspace absent: a human must grant that agent access to the workspace.
• Capability denied or revoked: stop retrying; a human must change the grant or reconnect it.
• Device code expired: run login again; codes last about 15 minutes.
• Temporary connection error: this is retryable, so it may succeed later. Wait between attempts and stop after a small number of retries.
• Artifact/import quota: follow the upgrade or cleanup path; do not loop.

See Troubleshoot an agent connection and Terminal states.

Nothing here matches

Email [email protected] with the artifact URL, team, workspace, expected and actual result, approximate time, and exact error. Never send credentials. See Contact support.

Questions and answers

What should I check first when work seems missing?

Verify the active team and workspace, clear list filters, and confirm workspace membership. If an agent created it, ask which workspace ID it used.

Should I reload when Markdown autosave is interrupted?

Keep the page open until connectivity recovers, then compare current content and History before reapplying text. Routine edits do not require manual saves or reloads.

When should I stop retrying an agent operation?

Stop on workspace or capability denial, revocation, quota exhaustion, or an expired or deleted artifact. A human decision or changed input is required.

Triage sequence

1. Verify the authenticated identity.
2. Discover scope with anima workspaces --json or the MCP workspace-discovery tool.
3. Confirm the workspace ID, artifact session ID, and required capability are not being confused.
4. Re-read current state before writing.
5. Classify the response as retryable, correctable, or terminal. A retryable failure may succeed later. A correctable failure needs changed input. A terminal failure cannot be fixed by repeating the same request.

Missing artifact

Run anima list --json to span all readable workspaces, then list --workspace <id> to narrow. If the intended workspace is absent, stop and request human approval. Do not probe or disclose private metadata.

Private-artifact denial

Signed-out humans must sign in; signed-in humans must verify account and team. Agents must verify workspace reachability. An artifact link never grants access. See Request access to a private artifact.

Markdown save or collaboration issue

Markdown autosaves. Do not instruct routine manual saves or reload-before-editing. On interruption, wait for connectivity, read the current content and History, then reconcile. Save/Command-S is a deliberate history checkpoint. Use History to recover an unwanted saved state.

Folder or ZIP import failure

Check the 50 MiB transport limit, 1,000-file limit, paths, archive integrity, structure, artifact type, and entry point. Exclude dependencies/build output. Correct source failures before retrying. Treat artifact-capacity refusal as terminal until the human resolves it.

URL/Figma import refusal

Free teams have five successful imports combined across URL and Figma. On exhaustion, relay the upgrade path and stop. Do not retry or imply deletion refunds allowance.

Duplicate uncertainty

Duplication is non-idempotent, which means repeating it may create another artifact. After timeout or lost response, list recent destination artifacts before retrying. Confirm the new artifact's workspace and session ID.

Publish failure

Require publish plus explicit human intent. Verify the current artifact state and returned public URL. A published site can lag current artifact edits until updated. Never publish as an assumed follow-up.

Review and notification failure

Use anima review list before reply or resolve. A missing destination may be deleted or no longer reachable. For a stale anchor, report it and use surrounding context; do not fabricate an anchor.

Retry matrix

For connection-specific codes and credentials, see Troubleshoot an agent connection. For escalation, prepare a privacy-safe handoff for [email protected]. Privacy-safe means it includes only authorized identifiers and does not reveal hidden owners, recipients, workspace names, or artifact existence. Use Contact support; never include credentials.

Questions and answers

Which identifiers must be separated during triage?

Confirm the workspace ID, artifact session ID, and authenticated agent identity before acting; do not substitute one identifier for another.

How should a retryable failure be verified?

Wait between a small number of retries, then read the resulting state. For create or duplicate uncertainty, list the destination before retrying.

When is a human decision required?

Stop and ask a human on workspace or capability denial, revocation, quota refusal, or a requested publication that lacks explicit consent.