🔍 What This Article Covers
Some customers have experienced Cloud Stack builds that fail with a Server Error 500 and remain stuck on the message 'Waiting for content generation to complete...'. This issue was caused by a platform-level bug that has since been resolved by our engineering team. This article explains what happened and what steps to take so your build completes successfully.
⚙️ What Caused the Error
This error was traced to an internal platform issue affecting the Cloud Stack build process. The engineering team identified and resolved the bug, and the fix has been deployed across the platform.
✅ Steps to Resolve
Because the underlying bug has been fixed, you do not need to change your build settings or recreate your project. Follow the steps below to successfully complete your Cloud Stack build:
- Retry the build. Attempt to run the Cloud Stack build again. The error should no longer occur now that the platform fix is in place.
💡 Tips If the Build Still Fails
- Make sure you are using the latest version of your browser and that no browser extensions are interfering with the platform.
- Try a different browser entirely if the issue persists.
- Wait a few minutes and attempt the build again, as occasional transient network issues can cause temporary failures.
🆘 Still Need Help?
If your Cloud Stack build continues to fail after following the steps above, please gather the following details before reaching out so our team can investigate quickly:
- Your domain or target keyword for the build
- A screenshot or screen recording of the error
If you need further assistance, please contact our support team so we can investigate further.