> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Saved vs live at the edge

> Why a setting you just saved isn't in force yet, and how to tell when it is.

Every settings screen in this section follows the same pattern. You press Save, allGood stores the value, and then it pushes a copy out to the network that actually enforces it. Those are two different moments, and the gap between them explains a lot of confusion.

<Tip>
  Just need the settings-level version of this pattern? [Set up Web Tracking on your site](/mk/settings/web-edge/tracking-setup) covers the same status chip in plain terms.
</Tip>

```
you press Save
   → the value is stored in allGood (this is the source of truth)
   → it is pushed out to allGood's global edge network
   → the write is read back and checked
   → only then does the screen say "Live at the edge"
```

## The status chip

Every settings screen and every published asset carries one.

| Chip                 | Means                                             |
| -------------------- | ------------------------------------------------- |
| **Publishing…**      | The change is on its way out                      |
| **Live at the edge** | Written, propagated, and confirmed by a read-back |
| **Publish failed**   | It didn't land. allGood retries automatically     |

For a removal — unregistering a form, unpublishing a page — the same states read **Removing…**, **Removed from the edge** and **Removal failed**.

<Frame caption="The status chip reading Live at the edge.">
  <img src="https://mintcdn.com/allgoodtechnologyinc/bf1LRHwyriZvgDxT/images/mk/web-edge/setup-edge-sync-chip.png?fit=max&auto=format&n=bf1LRHwyriZvgDxT&q=85&s=3c78067bf819d3da388dcc9be4e541fa" alt="The status chip reading Live at the edge" width="105" height="20" data-path="images/mk/web-edge/setup-edge-sync-chip.png" />
</Frame>

## How long it takes

Tens of seconds, with about a minute as the practical ceiling. The chip doesn't claim "live" until a read-back confirms it, so it's trustworthy rather than optimistic.

<Warning>
  Between pressing Save and the chip turning green, the **old** setting is still the one being enforced. This is the explanation for almost every "I changed it and nothing happened" report. Wait for green, then retest.
</Warning>

## One setting moves the chip on other screens

Your account's settings travel as a single bundle, so a capture request costs one lookup rather than several. A consequence worth knowing: saving on Consent Provider moves the chip on Form Processing too. They're the same underlying record, and nothing is wrong.

## Change history

Every settings screen has a change history at the bottom recording who changed what, and when. It's append-only.

<Frame caption="The change history at the bottom of a settings screen.">
  <img src="https://mintcdn.com/allgoodtechnologyinc/bf1LRHwyriZvgDxT/images/mk/web-edge/setup-settings-history.png?fit=max&auto=format&n=bf1LRHwyriZvgDxT&q=85&s=f14587c6f4017973e88bee98aefff375" alt="The change history at the bottom of a settings screen" width="1105" height="408" data-path="images/mk/web-edge/setup-settings-history.png" />
</Frame>

## If something looks stuck

A failed push is retried automatically, and a scheduled sweep re-checks values and repairs any that have drifted. If a chip has been amber for more than a few minutes, that's worth raising with [support@allgoodhq.com](mailto:support@allgoodhq.com) — there are admin tools that can rebuild an account's edge configuration on demand.