> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/general-guidelines/whatsapp-handling-errors/template-translation-not-found-error.md).

# Template Translation Not Found Error

### Overview

The "Template Translation Not Found" error occurs when a WhatsApp message is sent using a template language that is unavailable, unapproved, or does not match the language configuration approved by Meta.

WhatsApp message templates can support multiple language translations. Each language version is treated as a separate template translation and must be individually reviewed and approved by Meta before it can be used.

Important: Even if the template itself is approved, the specific language translation being used must also be approved and available. Otherwise, Meta will reject the message.

### Why Did This Happen?

When your application sends a template message, it specifies:

* The template name
* The language code (for example: en\_US, es\_LA, pt\_BR, etc.)

Before delivering the message, Meta verifies that the requested language version of the template exists and is available for use.

The message may fail for one or more of the following reasons:

* The requested language has not been added to the template.
* The language translation has not yet been approved by Meta.
* The language translation has been paused or disabled.
* The language code in the API request does not exactly match the approved language.
* The template translation was removed or is no longer available.
* The application is referencing an incorrect language configuration.

### How Meta Validates Template Languages

Every template message undergoes a language validation process before delivery.

Message Sent from Picky Assist

Meta Retrieves the Template

* Template name
* Template status
* Available language translations

Meta Validates the Requested Language

* Language exists for the template
* Translation is approved
* Translation is active
* Language code matches exactly

Validation Result

* Language translation found and approved → Message is delivered.
* Language translation unavailable or invalid → Message is rejected with a Template Translation Not Found error.

### How to Resolve the Issue

#### Step 1 – Verify the Template Language

Log in to Picky Assist.

Navigate to:

All menu → Settings → Channel → Templates

Locate the template and review the available language translations.

Confirm that the language you are trying to use exists in the template.

#### Step 2 – Check the Translation Approval Status

Review the status of the specific language translation.

Ensure that the translation is:

* Approved
* Active
* Available for use

If the translation is still under review, wait for Meta's approval before sending messages using that language.

#### Step 3 – Verify the Language Code

Confirm that your application or API request is using the exact language code approved by Meta.

Examples:

| Language                | Language Code |
| ----------------------- | ------------- |
| English (US)            | en\_US        |
| Spanish (Latin America) | es\_LA        |
| Portuguese (Brazil)     | pt\_BR        |

Even small differences in the language code may cause Meta to reject the request.

#### Step 4 – Check Whether the Translation Is Paused

If the language translation was previously approved, verify that it has not been:

* Paused
* Disabled
* Restricted by Meta

Paused translations cannot be used until they are restored to an active state.

#### Step 5 – Verify the Template Status

Navigate to:

All menu → Settings → Channel → Templates

Confirm that the template itself is:

* Active
* Enabled
* Not paused

Even if the language translation exists, the template must also be active.

### How to Prevent This Issue

Follow these best practices:

* Add all required language translations before launching campaigns.
* Wait for Meta approval before using a new translation.
* Verify language codes carefully when configuring templates.
* Test template messages after adding new translations.
* Regularly review template status in WhatsApp Manager.
* Update integrations whenever template language settings change.

### Frequently Asked Questions

**What is a template translation?**

A template translation is a language-specific version of a WhatsApp message template. Each translation must be individually reviewed and approved by Meta before it can be used.

**My template is approved. Why am I still getting this error?**

The template may be approved, but the specific language translation you are requesting may not exist, may not be approved, or may be inactive.

**Can I use a language that has not been approved yet?**

No. Messages can only be sent using language translations that have been approved by Meta.

**Does the language code need to match exactly?**

Yes. Meta requires an exact match between the language code in the request and the approved language translation.

For example:

* &#x20;en\_US&#x20;

Using an incorrect language code can cause message validation to fail.

**Can Picky Assist approve a template translation?**

No. Template approvals and translation approvals are managed entirely by Meta.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.pickyassist.com/general-guidelines/whatsapp-handling-errors/template-translation-not-found-error.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
