Skip to content
Support
  • There are no suggestions because the search field is empty.

Troubleshooting & FAQ

Table of contents:


FAQ: Common "How do I…"

How do I create my first app?

Open App Builder, create a new app, add one or more resources (a workflow, a table, or both), write a simple prompt, review the preview, then Save and Publish when you are ready. See Getting Started.

How do I get better results from my prompts?

Start simple. Describe the business outcome you want, mention the resource by its alias, and explain what the user should be able to see or do. If the first result is close but not correct, continue with a follow-up prompt instead of starting over. See Prompting & Best Practices.

How do I make changes to a published app?

Create a new version and make your changes there. The currently published version stays live until you publish the newer version. Only one version can be published at a time.

How do I use a workflow in App Builder?

The workflow should already be tested and executed at least three times before you use it as a resource. App Builder learns the workflow's output shape from recent runs, so a workflow with no meaningful execution history may not give good results. See Workflows.

How do I use a table in App Builder?

Add the table as a resource and give it a clear alias. Tables are often the easiest starting point because the fields are already structured and easier for App Builder to understand. See Tables.

How do I share an app with end users?

Publish the version you want users to run. After publishing, open the app from the App Library or use the app link that your team shares with end users.

How do I control what different users can see?

Use InApp Roles inside the app when you need app-specific visibility or behavior for different users. Use Vince Live roles to control who can access App Builder and related platform capabilities. See Security, Roles & Governance.

How do I limit users to only one app?

Use the App Builder permission level. Most users only need Run to use specific apps. Use Vince Live roles to scope which apps a user can see — typically one role per app or per business unit.

Should I use one app for all environments or separate apps for test and production?

You can use one app across environments if your workflows are set up with environment-specific runtime configuration — the workflow handles routing to the right environment behind the scenes. If your workflows aren't configured that way, or the data and behavior differ significantly between environments, separate apps are often easier to manage.

How long can I leave a build session open?

A build session stays active for up to 8 hours. If you've been away longer, refresh and start a fresh session — you can re-prompt from where you left off.

Why does my app generate slightly differently each time I prompt?

The AI is not deterministic — small variations between runs are normal. If the result is close but not quite right, refine with a follow-up prompt rather than retrying the same one.

Can I duplicate an app?

Not yet. If you want to build something similar to an existing app, create a new version within the same app, or start fresh and copy your prompts.

Troubleshooting: Access & sign-in issues

I can't see App Builder in the navigation

You may not have the App Builder permission yet. Ask your tenant administrator to confirm your Vince Live role includes the App Builder permission at the level you need (Read / Run / Write / Deploy / All). See Onboarding App Builder.

I get a session expired or 403 error

Your build session has likely timed out. Refresh the page, sign in again if needed, and start a fresh build session.

The chat is locked and I can't type

App Builder is generating your app — this is expected. The chat unlocks once the response is ready. If it stays locked for a long time, refresh and try again.

Troubleshooting: App issues (UI, binding, permissions)

The preview did not load or does not look right

Try a refresh first. If you were in a long editing session, save or exit and start a fresh build session. If the issue continues, review your latest prompt and simplify it.

I cannot edit the app

Another user may already be in an active build session for that app version, or the version may already be published. Create a new version if you want to continue editing.

My changes disappeared

Unsaved changes are not permanent. Make sure you click Save to keep the version changes you want.

The app shows an error after I changed something

If the app depends on a workflow or table that changed, the app may need to be updated and prompted again so it matches the new structure. See Prompting & Best Practices → Re-prompting when your resources change.

The app became unusable after a custom table was deleted

This is a known high-impact issue. If a selected custom table is deleted, the app may become corrupted and may not be repairable through the UI alone. In reported cases, the resource list had to be fixed through the API. Avoid deleting resources that are already used by live apps.

I cannot seem to complete custom-table setup through the UI

Some customers have reported that parts of the custom-table setup are difficult to complete cleanly through the current UI. If this blocks you, involve your implementation or admin team rather than trying to work around it blindly.

A user can open the app but should not see certain actions

Check the app-specific role setup and any Vince Live permissions involved. If the app uses both, they should be reviewed together.

A PDF or external content isn't showing in the preview

Generated apps run inside a sandboxed iframe, which can block some inline content like PDFs or third-party embeds. If users need to see a file, generate a download link or open it in a new tab instead.

InApp Roles aren't taking effect

This is a known limitation in the current beta. Confirm the role definition includes the right users and that your prompt explicitly tells the AI which behaviors to gate by role. Re-prompt and save. If it still doesn't take effect, contact support.

Troubleshooting: Workflow issues (trigger, mapping, errors)

My workflow is not working well as a resource

Make sure the workflow has been executed at least three times with realistic inputs. App Builder infers the workflow's output shape from recent runs, so a workflow with no meaningful execution history may not give good results.

The AI doesn't seem to know about my new workflow

New workflows need to be run at least three times before App Builder can use them. If you've added a brand-new workflow as a resource, run it a few times first, then re-prompt the app.

The app is not using the workflow the way I expected

Be explicit in your prompt. Explain what the workflow is for, what data it returns, and how the app should use that result.

I changed the workflow, but the app did not update

App Builder does not automatically rebuild the app when a workflow changes. Re-run the workflow a few times so the new output shape is registered, then go back into the app and prompt it again with what changed.

The workflow was removed or no longer works

If a resource used by the app is deleted or broken, the app may fail until the resource is restored or the app is updated to use something else.

Troubleshooting: Data issues (schema, search, relationships)

The app is showing the wrong fields

Review the table or workflow structure and make sure your prompt clearly asks for the fields you want. Clear aliases and cleaner field names usually help.

I added new fields, but they do not appear in the app

Changes to tables or workflows do not automatically appear in existing apps. Open the app again and prompt it to include the new fields or adjust the layout.

Search or filtering is not working as expected

Check whether the right field is being used for search or filtering. It often helps to prompt more explicitly, for example: "Add a search by supplier name" or "Filter by invoice status and date".

The app has trouble with related data

If the app depends on more than one resource, explain the relationship clearly in the prompt. For example, tell App Builder which resource is the main list and which one provides related details.

Why does customer-specific external data behave differently than expected?

If the app depends on customer-specific source structures, fields, or API definitions, generic assumptions may not work. In those cases, use the customer-specific definitions and validate the data path before refining the app.

Known limitations

  • App Builder is still evolving, so some behaviors and UI details may change.
  • Resource changes are not automatically reflected in existing apps — re-prompt to refresh.
  • New workflows must be executed at least three times before App Builder can use them.
  • Long or heavily iterative sessions can hit token limits — save often and start fresh when possible.
  • Deleting resources that are already bound to an app can cause serious recovery issues.
  • You cannot copy or duplicate an app. Use versions within the app instead, or start fresh.
  • Only one user can be in a build session at a time per app. Others see a "session in progress" message.
  • You cannot archive the only published version of an app — create a new version first.
  • You cannot edit a published version directly — create a new version from it.

When in doubt, keep the first version small, use stable resources, and improve the app step by step.

Where to go next