> ## Documentation Index > Fetch the complete documentation index at: https://wisty.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Fix common problems > Find the next step for connection, building, data, and sharing problems. Find the message or symptom below, then follow its next step. Keep the project open so you can check the result as you go. ## Salesforce shows a connection error In Wisty on the web, open **Connected orgs** and select the affected org. Open its actions menu and click **Reconnect**, then complete Salesforce authorization. If the initial connection fails, use **Try again** in the connection dialog. Check the package and access prerequisites in [Connect Salesforce](/docs/getting-started/connect-salesforce). Inside Salesforce, an expired Wisty session offers **Reconnect**. If that doesn't work, open Wisty again from Salesforce. ## I can open Wisty but can't build If you're working inside Salesforce, ask your administrator to check your **Wisty Builder** permission set and the org's Wisty setup. If you're working on the Wisty website, check that you're in the intended team. Web team membership and Salesforce builder permission are different access paths. See [Manage builders and viewers](/docs/salesforce-setup/control-access). A credit or subscription message needs the [workspace owner](/docs/billing/manage-subscription#who-manages-billing). Ask them to check **Plans & Credits**; running out of credits pauses generation for the whole workspace. ## A generation failed Click **Retry** below the failed generation. You can also choose another model before retrying. A failed generation isn't charged. A retry is a new generation and can use credits. See [Credits and plans](/docs/billing/credits-and-plans#what-uses-credits). To return to earlier saved work, follow the history and restore steps in [Work on a project](/docs/building/projects). Check the preview after restoring before publishing it. ## The preview won't load If the preview shows **Retry**, click it. If the problem continues, refresh the page. If the app itself shows an error with **Fix this**, use that action to ask Wisty to repair it. AI repairs use generation credits. Describe what you expected in chat if there isn't a repair action. For an app designed for a record page, click **No preview record**, enter a Salesforce record ID, and click **Apply**. Choose a record you can open in the connected org. See [Add an app to Salesforce](/docs/publishing/embed-in-salesforce). ## The app is empty or shows different records Check the app's filters and confirm that matching records exist in the org you're using. The first-app tutorial can be empty when you have no open opportunities closing this quarter. Then open a matching record in Salesforce as the same user. Wisty uses that user's Salesforce access, so two viewers can see different records in the same app. If the app uses the wrong object or field, tell Wisty the intended one in chat. Use an `@` mention to select the object. See [Describe what you need](/docs/building/describe-what-you-need). ## A Salesforce request is blocked On a desktop, open the project's **Network** tab and expand the failed request. * **Wisty blocked this call:** click **Open in Settings** when available. Enable the required access only if it belongs in the app, then save the change. If the endpoint isn't available in Wisty, ask for another way to build the feature. * **Salesforce returned an error:** check the error details. Use **Fix this** when offered for a query problem. A Salesforce permission error needs an administrator to review the user's access. Project settings don't override Salesforce permissions. See [Control Salesforce access](/docs/building/salesforce-access) for the controls and inspector. ## A record change failed or has an unknown outcome Check the project's write activity for the result. Salesforce validation rules, required fields, and permissions still apply to changes made through Wisty. If the result says **Outcome unknown**, open the record in Salesforce and check whether the change happened before trying again. Repeating it immediately could create a duplicate or apply the same change twice. Follow [Update Salesforce records](/docs/building/record-writes) for write access and approval settings. Changes made in the preview affect real records in the connected org. ## A shared app won't open If the page offers **Try again** for a connection issue, use it. For access problems, ask the app's owner or administrator to check the following: * The app is still published and shared with your team or Salesforce org. * You're signed in with the intended Salesforce user and org. * Salesforce Web is enabled for the host org if you're opening a web link. * The workspace subscription is active. If the page says **Salesforce Web is turned off**, an administrator must enable it before that link can work. Refreshing won't change the setting. See [Share and open apps](/docs/publishing/share-apps) for the viewing paths and [Connect a host org](/docs/salesforce-setup/connect-host-org) for administrator setup. ## Salesforce won't save Wisty's app policy Saving **App Policies** fails with `We couldn't save the external client app` and `state=MANAGED_INSTALLED` when **Wisty Builder** is in **Selected Permission Sets**. Salesforce doesn't allow permission sets from a managed package there. Remove it and select profiles or [a permission set you own](/docs/salesforce-setup/install#pre-authorize-users) instead. ## Get help Email [support@wisty.ai](mailto:support@wisty.ai) with the project name, the error shown, and the action that led to it. Say whether you're using Wisty on the web, inside Salesforce, or through a shared link. Include a screenshot if it helps explain the problem, with private record values removed.