You are here:
Builder Central (Beta) Limitations
Builder Central is a beta service, and some behavior is still evolving. Keep these limits in mind.
- Generative AI can be inaccurate. Review everything Builder Central produces before you deploy.
- During the beta, your builds and chat history are deleted after 7 days of inactivity. The 7-day timer applies to your whole workspace, not to individual projects, so any activity in Builder Central resets it. Work you've already published to a sandbox stays in that sandbox.
- Metadata visualization and editing are available only for the data model, agents, flows, Flexipages, and permission sets. Other metadata types aren't visualized or edited this way.
- Builder Central checks in with you as it works rather than pausing at multiple formal approval gates. Some early previews show multi-checkpoint flows, but that isn't the beta behavior, so don't rely on it.
- Preview orgs require a Developer or Developer Pro sandbox, so they aren't available when you build from a production org or a Developer Edition org. You can publish from full and partial copy sandboxes, but they don't provide preview orgs. Review your build in a sandbox instead.
- Design inside Builder Central is interface-only and doesn't read your org's data. Use a preview org to validate the app against real data. Agents aren't deployed to the preview org, so test an agent in your sandbox. Preview orgs don't include Data 360 data, even when Data 360 is provisioned for the sandbox, so test Data 360-grounded agents in your sandbox.
- For this release, use Builder Central's visual editing on a desktop. This refers to where you build, not to the type of app you can create.
- Occasionally, a raw error code, such as 429 or 503, can appear instead of a friendly message. If you see one, wait a moment and retry, or paste the error message in the chat and ask the agent to fix it.
Did this article solve your issue?
Let us know so we can improve!
