Releasing or publishing a page via Headless CMS or Releases can take a long build times
Tags: Headless CMS, Releases, FastStore
Keywords: Build, deploy, FastStore
When releasing or publishing a page via Headless CMS or Releases, you may experience long build times.
Solution
Follow the steps below to identify the root cause of publishing errors with the VTEX Headless CMS and Releases module.
Step 1: Check the release status
In the VTEX Admin, go to Storefront > Releases, and click Releases.
Check if the page release status is either Published or Failed.
Open the release and copy its identifier (e.g., 635feddd372d5fef67c4160e) at the end of the page URL (e.g., https://{accountname}.myvtex.com/admin/releases/calendar/?period=ONE_DAY-1708916400000&release=635feddd372d5fef67c4160e&search=&sort=LAST_MODIFIED&sort=DESC&status=ALL). After copying the identifier, proceed to Checking the GitHub pipeline to continue checking the status.
Step 2: Check the GitHub pipeline
After getting the Release identifier, follow these steps to verify the status of the corresponding build.
- Access the GitHub repository of your FastStore project.
- In the repository search field, search for the code obtained in the previous section. If you find a commit with the corresponding Release identifier in its name, it indicates that the Release has undergone the CI/CD process.
- Check the status of the Build check for the commit by clicking one of the following icons:
| Icon | Description |
|---|---|
| ✓ | The build was successful. If this status doesn't match what you see in the Admin, the communication between the Releases module and WebOps must have failed. No action is required, as this error is related to a communication issue on our end. |
| ● | The build is queued, waiting for other builds to complete. If queued for longer than 45 minutes, please open a ticket with VTEX Support. |
| ⨯ | The build failed. For more details, proceed to [Step 3 - Identifying the build error](#step-3 -identifying the build error). |
Step 3 - Identify the build error
If the Release's build failed, follow these instructions to identify the root cause of the error:
-
Click the Details link next to the Build check to view the full log.
-
Click the Re-run checks button to try deploying your Release again.
If the Re-run checks button is not available, you might not have write access to the repository. In this case, contact the repository's Admin.
-
If the error persists, review the build log, check the error, and open a ticket with VTEX Support with a description of the issue.