From the Page Groups screen, you can inspect the individual pages in any page group and investigate deployment errors or warnings.
View Pages in a Page Group
Click any page group row on the Page Groups screen to see all the pages it contains. The table shows each page's locale, page path, and the date it was last updated. Click the entity ID link in any row to open that entity's edit page directly, so you can make content changes without leaving the Pages workflow.
View Errors and Warnings
Click into a page group row, then select the Errors tab to see any deployment errors or warnings for that page group, along with guidance on how to resolve them.
There are two restrictions during these states:
- Publishing is disabled — The Publish button in the layout editor and global styles editor is disabled while a deploy is in progress or the site has errors. A tooltip explains why publishing is unavailable. You can still make and save changes locally; they will be ready to publish once the deploy completes or the error is resolved.
- Page group configuration is read-only — You can view page group configuration (scope, locales, URL template), but cannot modify it while a deploy is in progress or the site has errors.
Working During Deploys and Error States
You can continue working in the layout editor, global styles editor, and page group configuration while a deployment is in progress or your site is in an error state. A deployment indicator appears across all pages so you know when a deploy is active.
Common Errors
Path Conflict
What it means: Two or more entities have the same value for the slug field, which means they would generate identical URLs. Each page must have a unique URL.
How to find it: On the Pages tab, click the warning icon and open the Page Group Errors link. The Error Details section identifies which entities have conflicting slugs and the Source Data Update section shows what data change triggered the error.
How to fix it:
- For a one-off conflict, click the entity ID link in the page table to open the entity and update the slug field manually.
- For recurring conflicts (for example, if you have multiple locations in the same city and region, making their default URL paths identical), add a unique field to your URL template. For example, appending the entity ID makes the URL
/{address.region}/{address.city}/{entityId}, which is always unique.
Failed to Deploy
What it means: Something went wrong during page generation. This is often a backend issue, but check the following before contacting support.
How to fix it: Check one thing before contacting support. Each entity can only generate one page per site. If your page group scopes overlap, review and adjust the saved filters on each page group so they don't include the same entities. If the error persists after ruling this out, contact your account team for support.