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

# Why Are Events for Specific Users Missing on the Dashboard?

> Troubleshoot missing events for a small set of users caused by Fair Usage Policy (FUP) limit breaches, and confirm the block using Behavior analysis.

## Problem

Events are missing on the MoEngage dashboard for a small set of specific users, while the rest of your user base is unaffected.

## Explanation

When events are missing for only a few users, those users have likely breached the [Fair Usage Policy (FUP)](/user-guide/data/key-concepts/fair-usage-policy-fup) limits.

FUP limits apply per user. When a single user ID sends a high volume of data requests in a short window and crosses a MoEngage safety threshold, MoEngage temporarily blocks data tracking for that user ID to protect platform stability. Data for all other users continues to be tracked as normal, which is why the impact is limited to specific users.

If a specific user breaches any of the following thresholds, tracking for that user is temporarily blocked:

| Time Interval | Maximum Number of Data Requests Allowed | Action Taken If the Limit Is Breached                       |
| ------------- | --------------------------------------- | ----------------------------------------------------------- |
| 1 minute      | 100                                     | Blocks the tracked data of that user for the next 1 hour.   |
| 5 minutes     | 300                                     | Blocks the tracked data of that user for the next 1 hour.   |
| 1 hour        | 500                                     | Blocks the tracked data of that user for the next 24 hours. |
| 1 day         | 1000                                    | Blocks the tracked data of that user for the next 24 hours. |

<Warning>
  For any of the above time intervals, the limit breach can occur a maximum of three consecutive times before MoEngage imposes a 7-day block. If imposed, all data tracking for that specific user is suspended for a 7-day duration.
</Warning>

For the complete policy, including limits on user profile activity info and the number of devices per user, refer to [Fair Usage Policy Limits and Actions](/user-guide/data/key-concepts/fair-usage-policy-fup#fair-usage-policy-limits-and-actions).

<Note>
  Missing events can also be caused by an event being blocked or hidden globally in Data Management, which affects your entire user base rather than specific users. To rule that out, see [Why Are New Events or User Attributes Not Reflected on the Dashboard?](/user-guide/data/faqs-data/why-are-new-events-or-user-attributes-not-reflected-on-the-dashboard).
</Note>

## Solution

Use Behavior analysis to confirm whether a specific user breached an FUP limit.

<Info>
  **Prerequisites:**

  * Access to **Analyze** > **Behavior** and **Settings** > **Data Management**.
  * The affected user ID.
</Info>

Perform the following steps:

1. Confirm the event is active and not blocked globally. Go to **Settings** > **Data Management** and verify the event **Status** is **Allowed**. If you do not have access to Data Management, contact your workspace admin. For more information, refer to [Overview - Data Management](/user-guide/settings/data-management/overview-data-management).

<img src="https://mintcdn.com/moengage/F_suTfo98LMuaF6u/images/fup-data-management-page.png?fit=max&auto=format&n=F_suTfo98LMuaF6u&q=85&s=dfe74592f93a7183f1b22e952f7b9fb3" alt="MoEngage Data Management page showing event statuses set to Allowed." width="2880" height="1560" data-path="images/fup-data-management-page.png" />

2. Go to **Analyze** > **Behavior**. In the **Events & filters** section, select the event that appears to be missing for the user.
3. In the **Filter Users** section, select **Filter users by**. In the **Filter users by** list, click **ID** and enter the affected user ID.

<img src="https://mintcdn.com/moengage/F_suTfo98LMuaF6u/images/fup-behavior-filter-by-id.png?fit=max&auto=format&n=F_suTfo98LMuaF6u&q=85&s=0ea8f752c16c3ad9d412b8f0b98d226b" alt="MoEngage Behavior analysis with an event selected and users filtered by ID." width="2048" height="1044" data-path="images/fup-behavior-filter-by-id.png" />

4. In the **Behavior Options** section, in the **Analysis type** list, click **Total events**.
5. In **Duration**, select the period when the events went missing, and then click **Apply**.
6. Review the **Behavior chart**. Hover over the spikes to view the hourly or minute-by-minute breakdown of events.

<img src="https://mintcdn.com/moengage/F_suTfo98LMuaF6u/images/fup-behavior-chart-spike.png?fit=max&auto=format&n=F_suTfo98LMuaF6u&q=85&s=09d7bc918d655dfb1027f9871312b8be" alt="MoEngage Behavior chart with a spike of 535 total events in a single hour." width="2048" height="758" data-path="images/fup-behavior-chart-spike.png" />

If a spike shows a high concentration of requests in a short window (for example, 535 events in one hour), the user crossed the 500-requests-per-hour limit. This confirms that subsequent events for that user were blocked due to an FUP breach.