Limit Message Count

1 VersionUtility

Passes the first N messages of any stream t through unchanged, then stops pulling from the real upstream and emits nothing more, giving a hard total cap (not a rate) on how much an expensive downstream stage ever sees.

How it fits

Typical backends

A frame stream is capped to a fixed number of images before the expensive detector runs, so a single bounded batch is processed and then the backend idles.

An HTTP image source is bounded for a one-shot test run, with each forwarded message logged to confirm shape before stopping.

Caveats

State lifetimeOnce the cap is reached the component goes permanently dormant for the life of the process; there is no reset port or runtime reset, so a fresh batch needs a backend restart.
Hard constraintAfter the cap, an upstream producer with no other consumer can block forever because this component stops pulling real input.
Parameter interactionmax_count is constrained to one or more; a cap of zero is rejected at validation, so the component always forwards at least one message.
OrderingThe forwarded prefix is byte-identical and in arrival order; the component neither transforms nor reorders messages.

Versions

ccd249f8defaultlatest
Automated release
7/20/2026