Error TOO_MANY_REQUESTS_PER_DAY when using Event Monitoring API

Gloria

Updated May 22, 2026 00:48

Summary

When using the Data Pipeline Hub Event Monitoring API, you may receive the following response:

{
  "total_events_count": 0,
  "total_incomplete_events_count": 0,
  "error": "Code: TOO_MANY_REQUESTS_PER_DAY; Message parameters: [50]"
}

This means the tenant has exceeded the daily request limit for the Event Monitoring API. The value [50] indicates the configured daily limit being enforced.

Applies To Event Monitoring API

Endpoint:

GET /api/tenants/{tenantId}/monitoring/_eventMonitoring

Error code:

TOO_MANY_REQUESTS_PER_DAY

Cause

The Event Monitoring API has a daily request limiter. Historical engineering evidence shows the limiter is associated with EventMonitoringRequestsLimiter.

For this error:

Code: TOO_MANY_REQUESTS_PER_DAY; Message parameters: [50]

The configured limit is 50 requests per day for the affected tenant/context.

This limit can be reached through scheduled integrations, automation, recipes, Postman calls, or any other client that calls the same Event Monitoring API for the tenant.

Example Scenario

A recipe or automation runs every 30 minutes:

2 calls per hour × 24 hours = 48 calls per day

This leaves very little room for manual testing or retries. A few additional calls from Postman, scripts, or troubleshooting can push the tenant above the daily limit and trigger:

TOO_MANY_REQUESTS_PER_DAY

Does the limit vary by environment?

Retrieved evidence confirms this limit has been observed in both Production tenant and Development tenant

Resolution

Reduce the number of calls made to _eventMonitoring.

Recommended actions:

Avoid polling the endpoint too frequently.
Do not schedule calls every few minutes.
Use wider valid time windows instead of many small windows.
Coordinate manual testing so it does not overlap with scheduled automation.
Use _entityMonitoring only when troubleshooting a specific entity.
Increase max where appropriate instead of making repeated calls for the same time range.

Example optimized request:

GET https://{env}-data-pipeline-hub.reltio.com/api/tenants/{tenantId}/monitoring/_eventMonitoring?from={fromEpochMs}&to={toEpochMs}&detailed=Yes&max=1000

Workaround

If the limit has already been reached:

Pause scheduled jobs, recipes, and test scripts that call _eventMonitoring.
Wait for the quota to reset.
Resume with a lower call frequency.
Consolidate monitoring windows to reduce the total number of daily calls.

Do not retry the same request repeatedly, as retries may continue to count against the quota or keep the tenant at the limit.

Recommended Polling Pattern

Avoid a schedule like this:

Every 5 minutes = 288 calls/day
Every 15 minutes = 96 calls/day
Every 30 minutes = 48 calls/day

A 30-minute interval leaves only 2 additional calls before reaching a 50-call daily limit