Docs Connect Components Processors bounds_check bounds_check Available in: Cloud, Self-Managed Removes messages (and batches) that do not fit within certain size boundaries. Common Advanced # Common config fields, showing default values label: "" bounds_check: max_part_size: 1073741824 min_part_size: 1 # All config fields, showing default values label: "" bounds_check: max_part_size: 1073741824 min_part_size: 1 max_parts: 100 min_parts: 1 Fields max_part_size The maximum size of a message to allow (in bytes) Type: int Default: 1073741824 min_part_size The minimum size of a message to allow (in bytes) Type: int Default: 1 max_parts The maximum size of message batches to allow (in message count) Type: int Default: 100 min_parts The minimum size of message batches to allow (in message count) Type: int Default: 1 Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution bloblang branch