Updates and troubleshooting

Continue modifying the original product when improving a published experience. This preserves its identity and gives new content a clear validation and publication path.

Start with evidence

Use player feedback, product data or incidents to describe an outcome. For example: “New players often do not know what to choose in the first round. Inspect the instructions and action prompts.”

Give the connected assistant the product and relevant context. For analysis, ask it to distinguish observed facts from recommendations.

Running sessions remain fixed

Working content can change; generated runtime snapshots and formal versions are immutable. New changes need validation and must satisfy current publication requirements.

Existing rooms or sessions use their fixed content. Do not promise that a fix immediately changes every session already in progress.

Runtime errors

Record the product, time, visible error identifier, steps and expected result. Let the assistant use authorized troubleshooting tools to inspect diagnostics.

Repair the working content, validate and playtest as appropriate, then follow publication. Editing history or live state is not a substitute for a product fix.

Temporary unavailability

Read the product page's reason and next action. If the platform suspended a product due to runtime problems, address the issue and complete the required process before verifying availability.

For platform permission or service issues, use the available support or feedback entry. A submission receipt means the issue was recorded, not resolved.