Before changing more settings, identify what you expected, what happened, and where you were working.
Check your invited builder account, selected workspace, and the message shown by the builder. Creating an app can take time. Before retrying after a lost connection, inspect the project list to see whether creation completed.
Confirm that it saved successfully. Check which view or frontend you opened, then reopen the saved project. If a revision conflict is reported, reload and review the latest work before making the change again.
If the preview changed but the live app did not, inspect the published release and serving state. Saving is not publishing.
Check the selected table, view bindings, visible fields, search/filter state, and current user permissions. A filter can hide a record without deleting it. Do not make private information public simply to diagnose a display issue.
Preview and production use separate data. Production starts empty rather than copying the builder's sample records. See preview and production.
Read the reported status. Provider configuration, connection authorization, deployment version, and operator readiness can affect availability. Documentation cannot activate an unavailable feature or override a release hold.
Describe the action, the relevant screen, the visible message, and whether it affects preview or the live app. Include a project identifier or release number where useful, but leave passwords, API tokens, recovery codes, and private record contents out of support messages.
Return to: Quick start · Building guides · Glossary