Message templates — versions, editing and retirement

Who this guide is for: customer ADMINISTRATORS who write or manage WhatsApp message templates.

This guide explains what actually happens when you edit a template or retire one: every edit creates a new, unchangeable version in the same family; retirement is a one-way door; and approval of a version belongs to WhatsApp's parent company (Meta), not to anyone in your business — the product says so honestly.

About the evidence. The templates in the run behind this guide were test data. No template was ever submitted to the real Meta approval pipeline, and no live WhatsApp/Meta message was sent.

The template library

The template library lists each template by name, and the status filter narrows it honestly: choosing one status shows exactly that status's templates, not a fuzzy mix.

To edit a template is to add a new version

Editing a template never overwrites anything. The edit creates a new unchangeable version in the same family, and the family's history lists every version — earlier versions stay readable exactly as they were.

What this means for you:

Retirement — the one-way door

The library's delete action on a version is retire, not erase.

If your team sees a 409 META_APPROVAL_REQUIRED on a template action, it is this design working as intended — your seat manages the library; the approval status belongs to Meta.

What you see What it means What to do
409 META_APPROVAL_REQUIRED on retire The version's approval state is Meta's record and cannot be stepped past Check the version's approval status; do not retry the same action
A retired version missing from the draft view Expected — retired versions are frozen out Nothing to fix; earlier versions stay readable in the family history
Two reports with different wording Probably two versions of the same family Compare version numbers before assuming an error

What this guide does NOT claim (kept honest)


Evidence record (kept for honesty). The FULL3747-O14EV lane executed suite o14-ev3747-s4-campaigns-tpl-dest.pg.test.mjs — 24/24 cases passed — on the combined candidate checkout (C:/CT-ZC-FULL3747, branch codex/zcode-full3747), real compiled application over real loopback HTTP against a throwaway PostgreSQL 16 cluster (app role NOBYPASSRLS, row security forced). Verbatim case receipt: C:/CT-ZC-FULL3747/tools/zcode-integration3723/runtime/evidence/o14ev-s4/O14EV-S4-CAMPAIGNS-TPL-DEST-CASES.json (suite S4-campaigns-tpl-dest, started 2026-10-25T00:42:42.256Z); template cases cover matrix rows O11.04 and O11.06. Lane ledger (C:/CT-ZCODE-FULL3747/lane-o14ev-ledger.json) records: template SUBMIT/provider-status surfaces were exercised only to their provider-gated refusals — Meta submission is provider-gated and any APPROVED truth in the run was seeded SQL. Standing: local-candidate, test-harness evidence; Chief acceptance and publication OPEN; no live or Main-built deployment and no live Meta approval claimed.