> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/troubleshoot-errors/troubleshoot-common-whatsapp-api-errors/how-to-resolve-the-please-fill-all-fields-error-in-templates-on-doubletick.md).

# How to Resolve the "Please Fill All Fields" Error in Templates On DoubleTick

**How to Resolve the "Please Fill All Fields" Error in Templates**

![](https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FNuqe8fXDc1Ss589upsg4%2F0.png?alt=media)

Encountering the "Please fill all fields" error. This issue typically occurs when one or more required fields in the template are left blank. Follow this step-by-step guide to resolve it effectively:

**1. Understand the Error**

This error happens because the template requires certain information to function correctly. Mandatory fields are marked as essential to ensure all necessary data is included for proper operation.<br>

**Solution**

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2F2YKaGzc6IQhrL8Xapn3h%2F1.png?alt=media" alt=""><figcaption></figcaption></figure>

To resolve this issue, make sure that each required field is filled appropriately. You can input relevant keywords or placeholders, such as:

* **Name**
* **Text**
* **N/A**
* **Customer**

These inputs ensure that the system recognizes the fields as complete and allows the template to proceed without errors.

**2 . How to Resolve the "Body Example Should Not Be Present" Error**<br>

The "Body Explorer Should Not Be Present" error typically occurs when a variable is added within double curly braces, but the placeholder is left empty in the template. For example, {{}}.

![](https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FrcAIGIYIcxGzEtXOnSVw%2F2.png?alt=media)

Solution\
To resolve this issue, ensure that content is added within the {{}} placeholders. For example, use {{Text}}, {{Name}}, {{Customer}}, {{Id}}, etc.

![](https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FnmTCMbyjLPrSHfFvVyYY%2F3.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.doubletick.io/troubleshoot-errors/troubleshoot-common-whatsapp-api-errors/how-to-resolve-the-please-fill-all-fields-error-in-templates-on-doubletick.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.