BC-0148 · TROUBLESHOOTING
Editorial review 2026-09-26
Roblox Build Creations Are Missing
When expected Build creations are missing, verify the account, the visible inventory and the last known project identity before assuming deletion. A result that never completed, an empty list and a visible project that will not open need different next steps. Do not overwrite or recreate the project as a search method.
Symptom
Previously expected creations cannot be found in the account's visible Build inventory.
Immediate action
Preserve the last known project identity and verify the account and inventory state.
Diagnostic branches
- The account or visible inventory scope differs from the known creation context.
- Inspect the intended authorized context without transferring or recreating the project.
- The inventory is blank or loading rather than showing a completed list.
- Use that surface-state diagnosis before inferring project absence.
- The creation never showed a completed result.
- Follow generation-result diagnosis with the original request context.
- A project entry exists but cannot be opened.
- Use project-opening guidance rather than missing-inventory guidance.
- A known completed creation is absent from the intended inventory.
- Prepare an identity-and-history packet for official help without overwriting anything.
Least-destructive change
Locate existing identifiers and inspect the correct inventory without creating replacements or assuming a recovery control exists.
Retest
- The earlier creation state is known rather than inferred from an unsent idea.
- Inventory loading is not interpreted as a completed empty list.
- A public destination and an editable creation remain separate references.
Escalation
Contact official support with the known creation identity, last observed state and current inventory result if a completed project remains absent. Do not promise recovery or another purchase as a remedy.
Working notes
Start from evidence that the creation existed. Keep the known title or identifier, last observed working state and any published destination separately. A prompt you intended to send is not the same as a completed saved creation, and a remembered title may not identify the correct project.
Check that the intended account and available creation inventory are being viewed. Record any actual filter or scope the interface shows, but do not invent hidden tabs or folders. If the inventory is itself blank or still loading, resolve that display state before concluding it contains no projects.
Separate editing visibility from public visibility. A published destination and a private creation listing answer different questions. Keep either surviving reference without treating it as proof that the other surface must be accessible or that a removed public game was erased from every working state.
Avoid recovery claims the interface does not establish. A recycle bin, backup, autosave behavior and reconstruction of the same generated state are not established by this guide. The next action is to locate or report the known creation, not replace it.
Examples
- Project-location record: account label / known project identity / last observed completion or edit / current inventory state / public destination if known / exact error. Preserve identifiers privately for official help.
- Generation boundary: the earlier request never showed completion and no creation was located. Use generation-result guidance instead of describing a confirmed project as deleted.
- Inventory boundary: the project card is visible but selecting it fails. The creation is not missing from the list; use the opening-failure guide with that identifier.