Select Try again first. Landing page generation involves several steps in sequence, and a temporary failure in any one of them ends the run. A straight retry succeeds most of the time, and it costs you nothing because a failed build publishes nothing and counts nothing against your allowance.
In this article:
Step 1: Try again
The failure screen is titled Page generation failed, with the message Page generation failed — please try again. and two buttons: Try again and Back to setup.
Use Try again. It restarts the build with the same inputs.
If that fails, use Back to setup to change something rather than retrying the same thing a third time.
Step 2: Check the product
If your landing page is built around a product Atlas is creating from a link rather than one already in your catalog, that creation step is the most likely point of failure.
You may see one of these:
Couldn't create a product from your ad. Go back and pick a product from your catalog.Couldn't create a product from that link. Go back and try another link or pick a product from your catalog.
Both tell you the fix: use a product from your Shopify catalog instead. Add the product to Shopify manually, then rebuild and select it from the catalog. See Why couldn't Atlas import my product URL?
💡 Building from your Shopify catalog is more reliable than building from a link, because Atlas already has clean product data. If a link keeps failing, adding the product to Shopify takes two minutes and removes the problem for good.
Step 3: Simplify the angle
If you wrote your own angle, try a shorter one.
Very long angle text, text containing unusual formatting, or several conflicting instructions can stall the copywriting stage. A clear single-sentence claim plus a short list of supporting points is both more reliable and better input.
You may see Couldn't process your messaging angle. Try again. which points directly at this.
Rebuild with a simpler angle. If it succeeds, add detail back gradually.
Step 4: Check your research files
Try building once without research to see whether a document is the problem.
Watch for these while uploading:
What you see | What it means |
| Atlas could not extract text. The build continues without that file. |
| The upload itself failed |
| Too large |
| Wrong type |
Scanned PDFs are the usual culprit, because they are images with no readable text. Re-export from Word, Pages or Google Docs, or paste the text into a plain TXT file.
What the messages mean
Message | Meaning |
| The build stopped. Retry. |
| The same, from the variation flow |
| A general failure with no specific cause |
| Atlas cannot read your themes, so it cannot publish. Refresh before building. |
| The same problem, shown once you have started. The build never began, so nothing was generated and nothing counted against your allowance. |
Those last two are preconditions rather than build failures. Refresh the page, confirm Build page is available, and start again.
What you have not lost
A failed build publishes nothing, changes nothing on your storefront, and uses none of your published pages allowance.
Your project, its research, its saved personas and its settings are untouched. If you left the wizard part way through setting up, Atlas may offer Continue your unfinished landing page? when you return, telling you which step you were on.
If it keeps failing
Start a chat from the bubble in the bottom right of Atlas, or email support@helloatlas.io. Either way, include:
your store URL
the product you were building from, and whether it came from your catalog or a link
the format you chose, advertorial or listicle
the angle text you entered, if you wrote your own
the exact error message
roughly when you tried
The angle text and the product source are the two most useful details, because they are the two inputs most likely to be behind a repeatable failure.