Editing entries within the Visual Builder interface may fail to function correctly. This issue prevents users from restoring or using full editing capabilities while working in the interface.

This is typically caused by a version mismatch in the initialization method. Using an outdated version of the Live Preview SDK leads to compatibility failures within the Visual Builder.

1. Update the Live Preview SDK to the latest available version.
2. Verify that the init method in your code is aligned with the current implementation requirements.

After updating the SDK and the init method, open the Visual Builder and attempt to edit an entry. If the editing functionality works as expected, the issue is resolved.

When loading a shared preview link, interactive page elements—such as accordions, modals, or links—may become non-functional. This prevents stakeholders from fully testing the user experience within the preview context.

This issue is generally caused by external environment or public link (publink) configurations that interfere with client-side script execution, rather than a defect within Contentstack.

1. Verify if the shared URL is a valid public link and ensure it is loading successfully.
2. Coordinate with your development team to ensure the sandbox environment is configured to support interactive elements.
3. Check the preview link access settings to ensure all required scripts and styles are permitted to load.

Navigate to the shared preview link and attempt to trigger an interactive element, such as a modal. If these elements function correctly, the issue is resolved.

Active experiences created in the Visual Builder may fail to apply to a live website if the project exceeds the established personalization limits within the Content Delivery API (CDA). This results in only top-priority variants being displayed, while others are ignored during delivery.

The CDA has a hard cap on the number of active experiences allowed per request. Every experience passed in a request counts toward this limit (previously set to 5), regardless of whether a specific entry has a personalized variant defined for it. When a project contains more experiences than this cap, the additional variants are not rendered.

1. Review your project configuration to determine the total number of active experiences requested via the CDA.
2. Confirm if the total number of experiences exceeds the current system limit of 5.
3. Submit a request to Contentstack support to increase the personalization limit for your specific project (e.g., increasing the limit to 10).

Once the limit has been increased, reload the target page. If all active experiences are correctly evaluated and visible on the site and within the Visual Builder, the issue is resolved.