Troubleshoot Artifacts
Recover from sign-in, not-found, missing-content, revoked-access, version, and theme problems in Artifacts.
Start with the signed-in account, the approved link, and the last page that rendered successfully. Artifacts intentionally uses the same not-found boundary for several private states, so do not diagnose access by changing the URL.
The host redirects to sign-in
Artifacts is authenticated. Complete the standard Infra One sign-in with the exact account that owns the artifact or received the grant, then reopen the approved link.
If the browser returns to a different account, sign out and use the intended identity. Do not ask another person to forward their session, browser state, or private artifact URL.
The Artifacts host returns not found
For an ordinary account, the host is available only while at least one artifact is owned or explicitly granted to that account.
- Confirm that you signed in with the account named by the owner.
- Reopen
https://artifacts.infra.one/without adding a slug or query parameter. - Ask the owner through an approved private channel whether the grant is still active.
- If access should exist, preserve the time and the fact that the host returned not found, then contact support privately.
Do not send the artifact URL, slug, title, or content in a general support message. Do not try nearby slugs: not found deliberately does not distinguish an unknown artifact from private or revoked content.
The artifact is missing from Your artifacts
The list contains only artifacts owned by or explicitly granted to the current account and orders them by their most recent update.
- Confirm the signed-in account.
- Reload the index once in case a version was published after the page loaded.
- Ask the owner whether the artifact is still intended for your account and whether the grant remains active.
- If other artifacts remain visible but this one does not, treat the old link as unauthorized until the owner confirms otherwise.
The viewer contains no customer control for requesting or restoring a grant.
A link returns not found
The same response covers an unknown link, an artifact outside the current account’s grants, a revoked grant, and an artifact whose content has no stored version.
- Return to
https://artifacts.infra.one/and open the artifact from Your artifacts instead of editing the link. - If the card is absent, stop and ask the owner to verify access through the approved private workflow.
- If the card is present but the document frame cannot load, record the time and the visible title, then contact support privately. The artifact owner or approved operator must resolve missing content outside the viewer; viewers cannot repair it.
Never treat a copied URL as evidence that your account should have access.
Access was revoked while the page was open
A fresh list, page, or content request denies a revoked account. Content that was already rendered or copied is not remotely retracted.
- Close the artifact page and any downloaded or copied material.
- Do not refresh repeatedly or try a saved content URL.
- If the revocation was unexpected, contact the owner privately and wait for an explicit new grant.
- If the wrong person received access, follow the approved private incident process; a later revocation cannot recall content already seen.
The document looks outdated
The viewer serves the newest stored immutable version at request time. Reload the artifact once and confirm its title and updated date on Your artifacts.
If the old content remains, do not alter the URL or theme to find another version. Ask the owner whether a newer version was actually published. The public viewer exposes no version selector and cannot edit or publish content.
System, Light, or Dark has no visible effect
An artifact controls its own styles. Light and Dark add a theme marker only when the document has a recognized HTML root; System requests the document without an explicit marker. A document may not define different styles for those states.
- Select System, then Light, then Dark once each.
- Confirm that the selected control changes even if the document colors do not.
- Reload the page and try the intended theme once more.
- If the viewer control does not change or the frame disappears, preserve the visible title and time and contact support privately.
Do not add or edit query parameters other than the viewer controls; unsupported values fall back to System.
Interactive content or external resources do not work
Artifact scripts run inside an opaque-origin sandbox. The document policy blocks ordinary connection and media subresources, form submission, base-URL changes, and embedded objects. It expressly allows Google Fonts, inline scripts, and data images; a script can also navigate its own frame. This is an isolation boundary from the Artifacts host, not a zero-outbound or trusted-data-entry environment.
That restriction is intentional. Do not disable browser security, paste credentials into the document, or move the content to another host to make a blocked action work. Ask the owner for a supported non-artifact workflow when the document needs external data entry or network access.
What to include in a support request
Use an approved private channel. Include the signed-in account identity, whether the index or viewer failed, the approximate time, the visible error state, and whether the artifact still appears under Your artifacts.
Do not include the artifact URL or slug, private HTML, screenshots of sensitive content, credentials, browser state, customer data, or copied document output in a general support request.