---
id: "docs.en.troubleshooting"
translation_of: "docs.troubleshooting"
title: "Troubleshooting and recovery"
product: "shared"
scope: "creator-studio"
locale: "en"
audience: ["game-designer", "educator"]
content_type: "troubleshooting"
summary: "Recover from connection, agent, preview, import, simulation, source, and publish problems without losing work."
topics: ["error", "recovery", "connection", "agent", "preview", "import", "simulation", "source", "publish"]
tasks: ["recover-work", "retry-job", "repair-preview", "recover-import", "recover-publish"]
aliases: ["problem", "failed", "stuck", "reconnect", "rollback"]
prerequisites: []
related_ids: ["docs.projects", "docs.creator-playtest-publish", "docs.studio-test-publish"]
canonical_url: "https://mijnspel.com/docs/en/troubleshooting/"
alternate_urls: {"en":"https://mijnspel.com/docs/en/troubleshooting/","nl":"https://mijnspel.com/docs/nl/troubleshooting/","de":"https://mijnspel.com/docs/de/troubleshooting/"}
source_provenance: ["creator-dashboard/src/app/reconnect.js", "studio-server/src/reaper.rs", "creator-server/src/reaper.rs", "platform-browser/app-transfer.js"]
test_provenance: ["creator-server/tests/agent_flow.rs", "studio-server/tests/agent_flow.rs", "creator-server/tests/app_transfer_flow.rs", "studio-server/tests/publish_flow.rs"]
last_verified_commit: "22d2b3d1b5177fb46f81616a5042b47d54a0e38b"
last_verified_date: "2026-08-21"
---
# Troubleshooting and recovery {#troubleshooting}

Start with the smallest safe recovery: preserve the current project, read the visible status, and retry through the product UI. Avoid editing local databases or hidden agent state.

## Connection and running work {#connection-recovery}

After a temporary disconnect, wait for reconnect and refresh once if the UI does not recover. Running jobs are designed to resume or return to a safe queued state after a server restart. Do not launch repeated replacement requests while status is unknown. If work remains stuck, capture the visible project, chat, phase or queue state, and error text for support.

## Agent failure {#agent-recovery}

Read the last terminal message and technical details. Clarify missing requirements, then use the provided retry or send one focused follow-up. If the failure followed source edits, restore a known version or duplicate/export before further changes. Never place API keys in chat or project files.

## Preview and Play {#preview-recovery}

If preview is blank, confirm the latest build or proposal completed, reload Play, and inspect the visible error. Source syntax and unsupported assets are common project-level causes. Test in the authoring app before interpreting a publish failure.

## Import recovery {#import-recovery}

Keep the original archive. Retry from the project overview after confirming the upload completed and the product supports its version. An interrupted import is cleaned up rather than exposed as a half-created project. Do not rename archive internals or manually edit its version marker.

## Simulation recovery {#simulation-recovery}

Creator hides simulation controls until support is enabled and may hide them again when validation finds that the simulator no longer matches production rules. Studio always shows the Simulation tab, but it remains unavailable until the controller exposes compatible pure `legalMoves` support. Update or re-enable simulation through the agent, then run a small check before a long batch. Preserve the game version attached to results when comparing runs.

## Publish recovery {#publish-recovery}

Wait for the current candidate to reach a terminal state. On failure, verify Play again and retry only after addressing the reported cause. A previous public release may remain active while a candidate fails. Do not assume a pending domain or candidate is live until the product reports successful promotion.