Troubleshoot content block errors

This page describes some common errors when using Page Builder with content components.

Content components are centrally managed through the Component Service and rolled out across your Content Management instance.

There are times at which services can enter a transient state. As a Content Component maintainer, you can accidentally cause errors if you change a component version while editors are still changing a content page containing the earlier component version.

These troubleshooting steps can help you resolve issues you might encounter.

How to identify a content block error

Use these general steps to identify the block that contains the error.

  1. Look for the component with a ⚠️ in the title bar and the left-hand menu.

  2. The component banner shows a general error message.

    Some content variations should be reviewed.

  3. For the block with the issue, open the menu and look for the ⚠️ next to the variation.

  4. Select the variation that is reporting the issue.

  5. After the variation opens, the error changes to a more specific problem definition. Match the error to the list of documented Error types and solutions and complete the troubleshooting instructions to resolve the issue.

Error types and solutions

The error types in this section can be fixed by users who can understand the

Code issue preventing an upgrade to the latest version

This error is caused by the component structure in your content page not matching the required structure present in an updated component version. This common situation can happen when another Squiz DXP user has deployed an updated content component through the Component Service while you are editing component settings.

To fix the code issue preventing a component upgrade:

  1. Follow the steps in How to identify a content block error to find the content block containing the error.

  2. Select the edit the code here link to open the component code editor in the affected content variation.

  3. Make the suggested changes based on the error messages in the editor.

    The editor validates your changes in real-time to help you diagnose the issue.

  4. Select Apply changes to update the component settings and fix the code issue.

  5. Select Save to restart the component version upgrade.

    You can continue working on other content blocks if you prefer. However, restarting the upgrades as soon as possible is recommended to avoid other errors.

  6. Reload the content page asset to finalize the component upgrade.