Skip to main content
When a Horizon will not save or publish, the cause is almost always one of: network interruption, a validation issue, an asset upload problem, or a tier limit. Work through the symptoms below.
Cause. Network interruption between your browser and Brand Atlas.Fix.
  1. Check your network connection.
  2. Reload the page. If the editor reloads with your most recent changes intact, the auto-save was working; saving has resumed.
  3. If changes are lost on reload, the save did not complete. Re-apply the changes and confirm the save indicator returns to Saved.
  4. Check your email for an incident notice from us. See Status for the current channels.
Cause. The Horizon’s frontmatter is missing a required field, or a component is misconfigured.Fix.
  1. Read the validation message. It names the field or component at fault.
  2. Common causes: missing description, description longer than 160 characters, missing alt text on an image, an unrecognised component name.
  3. Fix the issue in the editor; the validation re-runs on the next save attempt.
Cause. Your tier’s active Horizon limit has been hit. You cannot publish a new Horizon without first archiving one.Fix.
  1. Open Horizons → Active. Identify a Horizon that has run its course.
  2. Archive it. The slot frees immediately.
  3. Publish the new Horizon.
  4. Alternatively, upgrade tier. Guardian’s 25-Horizon limit accommodates most use cases.
Cause. The image is too large, in an unsupported format, or the upload was interrupted.Fix.
  1. Check the file size. Per-file limits: 10MB for images, 25MB for asset files. Larger files should be linked rather than uploaded.
  2. Check the format. Supported image formats: PNG, JPG, SVG, WebP. Other formats need conversion.
  3. Re-attempt the upload. A weak network connection sometimes interrupts large uploads.
  4. If the file is genuinely necessary at a large size, write to support@brandatlas.pro for accommodation.
Cause. Brand Atlas embeds a fixed set of external video/audio sources. Other sources render as plain links.Fix.
  1. Check whether the source is supported (YouTube, Vimeo, Loom, Spotify).
  2. For unsupported sources, upload to a supported one and embed the link from there.
  3. For self-hosted video, upload to a hosting service and link.
Cause. The Horizon is still in draft state. Draft Horizons are visible only to the brand owner and assigned Editors.Fix.
  1. From the editor, click Publish (not just Save).
  2. Confirm the audience is set to include the team members who should see the change.
  3. Ask a team member to reload their browser; the change appears within seconds.
Cause. Someone else edited the Horizon while you were editing. The portal’s auto-save tried to write your version on top of theirs.Fix.
  1. The portal offers two options: Keep mine or Show me the conflict.
  2. Show me the conflict opens a side-by-side comparison. Pick the version you want, or merge by hand.
  3. To prevent recurrence, coordinate edits in real time. Brand Atlas does not currently support multi-user simultaneous editing on a single Horizon.

​
Recovering a lost draft

If a draft was lost during a session (browser crash, accidental close before save), check Horizons → Drafts. The auto-save runs every few seconds; a recent crash usually loses at most a few seconds of work. If the draft is not in Drafts, the auto-save did not run (very fresh draft, fewer than 5 seconds of work). Recreate the lost work.

​
When to escalate

Write to support@brandatlas.pro when:
  • The fixes above do not resolve the issue.
  • Saving fails on a Horizon that previously saved without problems.
  • You suspect data has been lost (a previously-published Horizon is now missing).
Include the Horizon name, the time of the incident, and any error message.

Visual editor

The editor reference.

MDX upload

Alternative authoring.

Editing and archiving

Lifecycle.