GuideReference3 min read
When something does not open
Use the symptom to find the right next step without losing your files, choices, or publication progress.
Select an underlined word to see what it means.
In this guide
The artwork or one of its Parts will not load.
Start by identifying the exact work revision and the file that failed. A missing response means the reader could not recover it. A wrong MarkA file's computed fingerprint, also called a digest or hash. A reader recomputes it to check the bytes.For exampleChanging the sketch's background color changes its Mark. A filename alone would not reveal that change.Full glossary entry → means it recovered different bytes. Those need different fixes.
| What you see | What to check next |
|---|---|
| Missing Part or catalog record | Confirm the exact version and selected-chain binding; resolve the missing Part. |
| Network or RPC read fails | Check the declared provider and whether the host permits that read path. |
| MarkA file's computed fingerprint, also called a digest or hash. A reader recomputes it to check the bytes.For exampleChanging the sketch's background color changes its Mark. A filename alone would not reveal that change.Full glossary entry → or length mismatch | Reject the returned bytes and recover the declared revision from a valid carrier. |
| Blank view but files verify | Check the runtime dependencies, browser features, and creator-code errors. |
| Only a thumbnail appears | Check whether the host supports the full interactive presentation. |
A mint, edit, or claim is refused.
Check the network and account, then the exact operation’s rules: supply, timing, access, current ownership, and any required administrator role.
An approved artist label, imported ABI, or token-transfer approval does not grant every contract action. A freeze cannot be undone through a presentation control.
A transaction or upload appears stuck.
Keep the current job and recovery record. Look up the operation’s receipt and actual state before assuming it failed. Resume the same publication once completed and unknown steps are reconciled.
A listing can lag the chain while the indexer catches up. Confirm the token and its bindings directly instead of minting a replacement.
The assistant or SDK reports an unavailable route.
Read the returned missing questions and blockers. Confirm that the configured Studio exposes the needed route and that its selected-chain PartsReusable components included in a work, with their own identities and permissions.For exampleSeveral artworks can share the same verified drawing library.Full glossary entry → exist.
Some operations are available only on certain networks. Keep your project and selected network while checking the chain guide for a supported path.
Technical detail: setup checks
Build the SDK checkout before launching its compiled MCP CLI. Check the workspace argument, Node version, and actual tools/list schemas. Pure project planning needs no Studio endpoint. Staging and private draft operations need the configured Studio and scoped credential. Staging requires a Studio endpoint that accepts project uploads.
Keep enough information to reproduce the issue.
Record the guide or operation you followed, the selected network, work revision, public contract/token references, failed resource, and exact error. Include whether the issue occurs locally or in a particular host.
Keep signing secrets and private credentials out of a report. Preserve original files and the existing recovery record while investigating.