---
title: Limitations for Streaming Video & Ads
source: https://docs.newrelic.com/docs/streaming-video-&-ads/limitations
---

This page consolidates known limitations, unsupported behaviors, and constraints across the Streaming Video & Ads feature set. For full context on each limitation, follow the links at the end of each section.

## Custom widgets [#custom-widgets]

### Widget limit [#widget-limit]

Each account supports a soft limit of **50 custom widgets per dashboard context** — 50 for **Video quality metrics** and 50 for **Ad quality metrics**, counted separately. If you reach the limit, delete an existing custom widget before adding a new one. Your existing widgets continue to function normally.

### NRQL query patterns [#nrql-patterns]

The dashboard filter integration works well for common query patterns. The following NRQL patterns have limited or untested support and may produce unexpected results when global filters are active:

-   **OR conditions in `WHERE`** — Queries with `OR` logic in the `WHERE` clause may produce incorrect results when global filters are applied, due to operator precedence.
-   **`COMPARE WITH`** — Time-comparison queries may not work correctly with the dashboard time picker integration.
-   **Subqueries** — Nested `FROM (SELECT …)` patterns may not behave as expected when global filters are applied.
-   **Complex nested aggregators** — Advanced `filter()` constructs beyond the documented examples may not handle the no-filter state correctly.
-   **`PREDICT` clause** — `PREDICT` clause queries may not work correctly with the dashboard time picker integration.

If you encounter a query pattern that doesn't work as expected, contact your New Relic account team with the query details.

For full context, see [Create custom widgets for streaming dashboards](https://docs.newrelic.com/docs/streaming-video-&-ads/custom-widget-support).

## Obfuscation [#obfuscation]

### Roku regex patterns [#roku-regex]

Roku uses `roRegex` for pattern matching. Roku doesn't support complex lookahead/lookbehind assertions. Patterns that are valid in JavaScript or Java regex may need to be simplified for Roku.

For full context, see [Obfuscate streaming media agent data](https://docs.newrelic.com/docs/streaming-video-&-ads/obfuscation) and [Roku obfuscation rules](https://docs.newrelic.com/docs/streaming-video-&-ads/installation/roku/obfuscation-rules).

## Service maps [#service-maps]

### Entity linking requirements [#entity-linking]

Linking a media streaming entity to a Browser or Mobile entity requires exact attribute matching. See [Service map for Streaming Media & Ads](https://docs.newrelic.com/docs/streaming-video-&-ads/view-data-in-newrelic/streaming-video-&-ads-single-application-view/service-maps) for the full requirements.

## Agent migration [#agent-migration]

### Dual event types during migration [#dual-event-types]

Migrating to version 3.xx of the media agent may result in dual event types during an interim period. See [Update the media agent](https://docs.newrelic.com/docs/streaming-video-&-ads/update-the-media-agent) for management guidance.