BC-0163 · TROUBLESHOOTING
Editorial review 2026-09-26
Build Finished but the Game Is Missing
When generation showed completion but the game cannot be found, reconcile the completion evidence with the destination it identified. Confirm which request and project finished, inspect any actual result link, and distinguish an absent listing from a game that opens but fails to load. Do not pay to recreate it merely to investigate visibility.
Symptom
A completion or result acknowledgement was actually observed, but the expected game is not located.
Immediate action
Match the completion acknowledgement to its original request and any actual result destination.
Diagnostic branches
- The acknowledgement describes an update to an existing game.
- Inspect that game instead of assuming a new listing should exist.
- An actual result destination opens the expected game.
- Record the separate listing issue and preserve the accessible result.
- The identified game opens but cannot reach a playable state.
- Use loading diagnostics with the known project identity.
- No matching destination or listing can be located.
- Prepare the completion reconciliation record for official assistance.
Least-destructive change
Use the observed completion receipt to locate existing work before repurchasing, publishing or regenerating anything.
Retest
- The completed operation is classified as a new creation or an update only when its evidence supports that distinction.
- Destination access and listing presence are checked separately.
- The original result is not replaced just to test whether another request appears.
Escalation
Provide official assistance the completion wording, available identifiers and separate destination/listing outcomes. Include charge evidence only when actually present; no refund or recovery outcome is promised.
Working notes
Preserve the completion wording or result acknowledgement and the prompt it followed. A chat response saying that a change was made is not necessarily proof that a separate new creation was produced. Establish whether the operation updated an existing game or claimed to finish a new one.
If the interface provides a result link or project identifier, compare it with the creation you are trying to locate. Do not construct guessed URLs or share private access tokens. A matching destination that opens establishes a different problem from a result with no accessible destination.
Check the current account and ordinary creation listing for that identified result. Note whether it is absent from the list, listed under an unexpected title, or present but inaccessible. This is a reconciliation task: do not change visibility or publishing settings just to make an unlocated private creation appear publicly.
Keep any financial observation separate from the completion record. If an actual charge and missing result coexist, use the charged-without-game guidance with both records. A vanished listing alone neither proves a charge nor establishes that regeneration will recover the original.
Examples
- Completion reconciliation: acknowledgement belongs to an update on the existing game, while the reader expected a new listing. Inspect the updated project before searching for a second creation.
- Destination comparison: the completion link opens the expected game, but the current listing does not show it. Record a listing discrepancy rather than saying no game was generated.
- Missing-result packet: exact completion wording / original request / account context / available result identifier / destination outcome / listing outcome. A destination that opens to a loading error routes to loading diagnostics, not another generation.