> ## 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 is not in force yet, and how to tell when it is.

Every settings screen in this section follows the same pattern. You select Save, allGood stores the value, and then it sends a copy to the servers that enforce it. Those are two different moments, and the gap between them explains a lot of confusion.

```
you select Save
   → the value is stored in allGood
   → it is sent to allGood's servers around the world
   → allGood checks that each server has the new value
   → 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** | Saved, sent everywhere, and checked |
| **Publish failed** | It didn't land. allGood retries automatically |

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

![The status chip reading Live at the edge](https://mintcdn.com/allgoodtechnologyinc/bf1LRHwyriZvgDxT/images/mk/web-edge/setup-edge-sync-chip.png?fit=max\&auto=format\&n=bf1LRHwyriZvgDxT\&q=85\&s=3c78067bf819d3da388dcc9be4e541fa)

The status chip reading Live at the edge.

## How long it takes

Tens of seconds, with about a minute as the practical ceiling. The chip doesn't claim "live" until it has checked, so you can rely on it.

> [!WARNING]
>
> Between selecting 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.

## 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. Entries can't be edited or deleted.

![The change history at the bottom of a settings screen](https://mintcdn.com/allgoodtechnologyinc/bf1LRHwyriZvgDxT/images/mk/web-edge/setup-settings-history.png?fit=max\&auto=format\&n=bf1LRHwyriZvgDxT\&q=85\&s=f14587c6f4017973e88bee98aefff375)

The change history at the bottom of a settings screen.

## If something looks stuck

If a change fails to arrive, allGood retries it automatically. It also re-checks every setting on a schedule and fixes any that don't match. If a chip has been amber for more than a few minutes, contact [support@allgoodhq.com](mailto:support@allgoodhq.com). allGood support can also rebuild your account's settings on demand.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.