Configure message time-to-live | Developer Documentation

Plan WhatsApp message validity with ChatArchitect

Use this checklist for an offer, reminder or update that becomes useless after a deadline. Confirm the timing of your connected sending workflow and ask support what delivery validity controls apply before relying on an expiry setting.

Understand the different times

Meta uses time-to-live (TTL) for the period during which WhatsApp retries delivery of a message that has not reached the recipient. Its TTL reference describes different API support and ranges for different template categories. Customer access to a TTL setting in wtargeted.com or a ChatArchitect integration has not been confirmed.

Putting an end date in the template text or a campaign document does not configure WhatsApp TTL. Check the sending workflow and delivery settings separately. Meta drops undelivered messages when their applicable TTL expires; the visibility and timing of that outcome in your connected tool need to be checked.

Before scheduling a time-sensitive message

1. Record the business deadline and time zone. Check that the template text, variables and button destination describe the same current terms.
2. Find the approved template and language in wtargeted.com. Check its final category; use the category guide if it differs from the intended purpose.
3. Check when the connected workflow submits the message, which local queues or retries it uses, and who can change that schedule.
4. Ask ChatArchitect support whether TTL can be configured for this template and integration. Confirm the current value, supported range, where it is set, which messages a change affects, and how expiry can be identified.
5. Choose a send time that leaves room for the expected workflow and delivery delays. If the available controls cannot meet the business deadline, revise the timing or wording before sending.

For example, if an offer ends on 21 October at 18:00 UTC and the planned submission is at 17:50 UTC, only ten minutes remain before the offer ends. This example does not establish that a ten-minute TTL is available for a marketing template or that every queued message can be cancelled.

Check attempts before sending again

Use the sending guide to identify the original attempt and inspect any later result. If the integration does not expose an outcome, record it as unknown and ask support to check the reference. Do not infer expiry merely because the recipient has not replied.

If the original attempt remains pending when the business deadline passes, ask support or the workflow owner which actions can stop new submissions and what happens to already submitted messages. Pausing a local campaign does not establish cancellation of an attempt already accepted by WhatsApp. Treat an already delivered message separately from a pending one.

Check the cause before agreeing on another attempt. A reported recipient marketing limit has its own retry guidance. Confirm that the information is still useful and the recipient expects it; do not send expired offer conditions.

Recheck after a template or workflow change

If a custom TTL has been confirmed for your workflow, ask support to recheck it after a template category change or an account/integration change. Meta documents that automatic category updates can clear a custom TTL. Record the newly confirmed value and test the intended sending selection before relying on the previous timing.

For a support request, provide the connected tool, sender number, template name and language, final category, business deadline, scheduled and actual attempt times with time zones, available attempt reference and result. Keep App key and Secret out of screenshots and diagnostic messages.