An artifact won't open or looks stuck

Most artifact problems clear up with a reload, a short wait, or a fresh sign-in. Find your symptom below and apply the matching fix.

You see "Failed to load artifact"

The artifact could not be fetched — usually a temporary connection hiccup. Reload the browser tab. If the message returns, close the artifact and reopen it from your projects or from the chat message that created it. You know it worked when the content renders instead of the error.

The artifact stays on "Working..." or "Updating"

The Co-Pilot is still writing, or a background analysis of new recordings has not finished yet — artifacts built on a discussion wait for that analysis. This is normal for long discussions; see How long does processing take? for what runs when. Leave the artifact open: the label disappears and the content refreshes on its own when the work completes. If nothing changes long after processing should be done, reload the tab. You know it is resolved when the label is gone and the latest content shows.

You see "Redirecting to sign in..."

The artifact requires an account, and you are not signed in — or your session expired. Sign in with the account that was given access, then open the link again. If it still will not open, the link may be view-only or limited to specific people; ask the person who shared it to check the sharing settings — see Who can see your work: visibility levels. You know it worked when the artifact opens after signing in.

Still stuck?

The best way to report it: in the app, open ? → Send Feedback — it automatically includes where you were on the platform and lets you attach a screenshot of exactly what you see. Alternatively, use the contact form.

Related articles

• How long does processing take?
• Who can see your work: visibility levels