1Footer documentation
Understand delivery and repair status
Tell saved access, queued maintenance, paused delivery and verified public output apart.
Last reviewed
Read the latest delivery result
Connection, deployment and public delivery are separate checks. Where a status is shown, read it with the website, current publication and check time. Status wording can differ between delivery integrations.
| State | What it tells you | What happens next |
|---|---|---|
| Not connected | This delivery path does not have saved access for this website. | Connect the publishing account for the current destination, or install a released delivery package. |
| Saved / queued | Access was saved or work is waiting. The public footer has not yet been confirmed. | 1Footer can process supported managed delivery in the cloud; check the later delivery result. |
| Repairing / verifying | A supported repair or its checks are still running. | Wait for the public result. Avoid starting duplicate publishing operations. |
| Verified | A public check matched the publication and website state checked at that time. | Check again after content, targeting, connection or platform changes. |
| Paused | Delivery or automatic repair was intentionally paused. | Keep the pause if it is intentional. Resume deliberately, then confirm the new public result. |
| Needs attention | The repair could not safely finish, for example because of missing access or a conflicting edit. | Review the affected website, fix the cause and check again. A failed check is not a successful repair. |
A previous success has a date
A verified result describes the page and publication observed during that check. It does not prove a later footer edit, DNS change, theme update or project migration is already live.
A successful provider build or deployment is useful progress, but the public website still needs its own delivery check. Use the verification guide to compare actual HTML, links and route behavior.
Retry and recovery stay within the connected site
Supported repairs keep progress in the cloud and check uncertain provider outcomes before starting another write. Failed supported deployment repairs can restore the prior deployment. Pauses, account ownership and source conflicts still apply during recovery.
There is no universal repair-time guarantee. Revoked access, an unavailable provider or an unreleased native adapter can prevent completion. The platform guide lists current availability.