## **🔍 What causes batch edit failures?**

Website Studio processes page edits and publishing through background tasks. Large or multi-part batches may exceed execution time limits or fail while processing pages in sequence.

Publishing can also fail when an image or other asset is missing, blog content was not saved, or generated build files do not pass validation. As a result, some pages may update while others keep their previous layout or styling.

## **✅ Check which pages were updated**

1. Open **Website Studio** from the left sidebar.
2. Review each affected page individually.
3. Confirm whether the header, alignment, content, and other requested changes were applied.
4. Record the pages that were successful and the pages that still need changes.

Do not assume that a completed task updated every page in the batch. Always verify the result page by page.

## **📦 Use smaller edit batches**

1. Separate large requests into smaller groups, such as three to five pages.
2. Apply one type of change at a time when possible.
3. Wait for one group to finish before starting the next.
4. Refresh the affected pages and confirm the changes before continuing.

For example, if only three of ten pages were updated, leave those three completed pages unchanged and retry the remaining seven in smaller groups. This reduces timeouts and makes failed pages easier to identify.

## **📄 Check content and asset references**

Before publishing, confirm that each page has saved content and that referenced images, files, and other assets still exist. Missing assets or unsaved blog sections can prevent the build from completing.

- Open each affected page and save any pending content.
- Replace missing or broken images and file references.
- Check that blog sections are present and persisted before publishing.
- Avoid removing or renaming assets while a build is running.

## **🚦 Resolve an orange publishing status**

An orange status that remains after a failed attempt usually means the background publishing task did not finish successfully. It may not update automatically until a later task completes.

1. Wait briefly for the current background task to finish.
2. Refresh Website Studio and review the status again.
3. Check the page for missing content, assets, or layout changes.
4. Retry publishing only after correcting any issues.
5. Publish a smaller group instead of resubmitting the entire batch.

Avoid repeated retries while the same task is still running. Repeated submissions can create overlapping tasks and make the final status harder to interpret.

## **🧪 Confirm the final result**

- Open every page included in the batch.
- Check headers, alignment, spacing, content, links, and images.
- Confirm the published version, not only the editor preview.
- Record any page that remains unchanged or shows an outdated status.

## **💬 Get help with an unresolved failure**

If a smaller batch still fails, note the affected page URLs, the requested changes, the current status color, and any visible error message. This information helps the team investigate the background task and build result.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be instantly connected with a member of our team.