CONNECT EAP

Stream Management instance limits

Save PDF

Stream Management instance limits

Save PDF

Last UpdatedOct 27, 2026
3 minute read

This guide summarizes limits on resources and operations in a single Stream Management instance. Limits are grouped by whether they apply to an instance, an individual request, or a resource definition. Values that vary by instance are identified.

Instance limits

These limits apply to the total resources in one instance. Limits marked as varying by instance depend on your provisioned capacity.

Limit	Value	Applies to	Considerations
Stream types per instance	500	One Stream Management instance	Counts all stream types defined in the instance.
Streams per instance	Varies by instance	Total streams defined in one instance	The configured stream-creation gate is distinct from overall instance capacity. Reaching the instance limit will return 400 Bad Request. Contact AVEVA support to confirm your capacity.
Stream views per instance	No enforced limit	Total stream views defined in one instance	No per-instance stream-view count limit is enforced. This does not mean that instance resources are unlimited.
Data points per instance	No enforced limit	Total data points stored across all streams in one instance	No aggregate per-instance data-point count limit is enforced. Storage and instance capacity still apply.

Request limits

These limits apply to individual requests. Some depend on instance configuration. Contact AVEVA support to confirm the values for your account.

Limit	Value	Applies to	Considerations
Summary or sample intervals	100,000 intervals	One summary or sample request	This is the maximum supported interval count. Exceeding this limit returns 400 Bad Request.
Bulk delete streams	1 stream	One bulk delete request	Exceeding the applicable limit returns 413 Request Entity Too Large.
Bulk security tag update	500 streams per request	One bulk security-tag update request	Exceeding the applicable limit returns 413 Request Entity Too Large.
Data read count	2,500,000 data points	One non-bulk data read	Counts events accessed during processing, not just values returned. Exceeding the applicable limit returns 400 Bad Request.
Bulk read streams	Varies by instance	Streams included in one bulk data-read request	This limit applies to bulk data reads, not requests to read stream definitions. Exceeding the applicable limit returns 413 Request Entity Too Large.
Bulk read count	Varies by instance	Events accessed across streams in one bulk data-read request	The total allowance is divided across the distinct streams. See the read-count guidance below.
Concurrent requests	Varies by instance	Requests processed at the same time	This limits simultaneous in-flight requests, not requests per second. Excess requests return 429 Too Many Requests.

Read-count limits

Read-count limits apply to the events accessed while processing a read, not only to the values returned. A request that exceeds the applicable limit returns 400 Bad Request; it is not an empty-result response.

Request type	Applies to	Considerations
Non-bulk stream data reads	/api/v2/Streams/{streamId}/Data/{operation} Includes Range, Window, Summaries, Sampled, and Interpolated operations	Subject to the non-bulk data read count above. Summary or sampled results may require accessing more events than are returned.
Bulk stream data reads	/api/v2/Bulk/Streams/Data/{operation}	The configured total event allowance is divided by the number of distinct streams, rounding down to a per-stream allowance. For example, an allowance of 500,000 events across four streams gives 125,000 events per stream. The applicable total depends on your instance.

Request type

Applies to

Considerations

Non-bulk stream data reads

/api/v2/Streams/{streamId}/Data/{operation}

Includes Range, Window, Summaries, Sampled, and Interpolated operations

Subject to the non-bulk data read count above. Summary or sampled results may require accessing more events than are returned.

Bulk stream data reads

/api/v2/Bulk/Streams/Data/{operation}

The configured total event allowance is divided by the number of distinct streams, rounding down to a per-stream allowance. For example, an allowance of 500,000 events across four streams gives 125,000 events per stream. The applicable total depends on your instance.

To avoid exceeding read-count limits:

Use the non-bulk route for single-stream requests.
Reduce the number of streams in each bulk request.
Reduce the interval count.
Split long time ranges into smaller requests.
Handle limit-exceeded responses separately from empty results and retry with a smaller request.

Resource definition limits

These limits apply to individual property values or definitions.

Limit	Value	Applies to	Considerations
Resource identifier	250 characters and 487 UTF-8 bytes	Stream, stream type, and stream view IDs	Both limits apply. The first one reached determines the maximum length.
Resource name	250 characters	Object display names	Character limit.
Resource description	2,000 characters	Object descriptions	Character limit.
Secondary-index identifier	503 UTF-8 bytes	Combined stream ID and indexed type-property ID	The stream ID and property ID share this encoded-byte limit.
Serialized stored object	256 KiB	Each individually stored SDS object, such as a stream, type, or view definition, or a security-tag/owner map item	Applies to each serialized object individually. It is not an aggregate per-stream limit for metadata or tags.
Type property nesting depth	3 levels	One stream type definition	Properties beyond the third level are rejected.

For IDs, both character and UTF-8 byte limits apply. Non-ASCII text may reach the byte limit first: Japanese kana commonly use three UTF-8 bytes and emoji commonly use four.

For a secondary index, the stream ID and indexed type-property ID share the 503-byte budget. A stream ID near its own 487-byte limit leaves correspondingly less space for the indexed property ID.

Account-specific limits

To learn about the specific limits that apply to your account, contact AVEVA Support.

CONNECT EAP