---
title: "Known Issues"
slug: "moengage-known-issues"
updated: 2025-07-17T20:26:19Z
published: 2025-07-17T20:26:19Z
canonical: "support.jacquard.com/moengage-known-issues"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.jacquard.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Known Issues

Please be aware of the following issues you may encounter whilst using Jacquard with MoEngage:

- If your human control variant contains personalisation variables, then it will require a different fallback method to the **| default** filter. Instead use an if statement:

```plaintext
{% if variants.variant_text == blank or variants.variant_text == null %}
PASTE YOUR HUMAN CONTROL HERE
{% else %}
{{variants.variant_text}}
{% endif %}
```
- ContentAPI code snippets can't be stored in **Content Blocks** so you will need to store the code snippets for the subject line and open pixels outside of the platform.
- Maximum **Throttling limit** is 60000 requests per minute.
- Jacquard Dynamic Optimisation Start Schedule must be at least 30 mins before the MoEngage deployment begins.
- When testing your email message in MoEngage, you must send to a **custom segment** (not an individual email address) in order for the API calls to be made.
- Avoid using double quotation marks in the default fallback language.
- Talk to your MoEngage customer success representative to ensure the open tracking pixels returned via the ContentAPI are not HTML encoded.