Skip to content

WA_NLT_UNRESOLVED

Category: whatsapp  ·  Severity: warning  ·  Channel: WhatsApp

After rendering body_nlt against the sample contact, one or more NLT expressions could not be resolved. At send time the recipient would see the raw expression text in place of the value.

What it means

WhatsApp Inspect renders your template's body_nlt against a sample contact. If an NLT expression can't be resolved — usually a typo in a property name, or a property the sample contact doesn't have — the raw token is left in place rather than substituted.

Note

This check only reports NLT expressions. Meta's own positional placeholders ({{1}}, {{2}}, …) are deliberately excluded here — those are validated separately by WA_VARIABLE_COUNT_MISMATCH and the placeholder-sequence checks, so they are not double-flagged as unresolved NLT.

Unlike a required miss, an unresolved expression does not suppress the message — it still sends, but with the literal token text visible.

Why it matters

An unresolved NLT expression means the recipient sees something like Hi «first_name» instead of their name. Because the message still delivers, the problem is easy to miss until a recipient reports it.

How to fix it

  1. Check the expression syntax — confirm the property name is spelled correctly and matches a real contact property.
  2. Confirm the property exists on the contacts this template targets, or add an NLT fallback value.

Finding context

json
{
"expression": "first_name"
}