[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-15 UTC."],[[["This page documents the `FlowController.MaxOutstandingElementCountReachedException`, an exception that occurs when client-side flow control limits are reached based on the number of in-memory elements."],["The page lists the available versions of this exception, ranging from version 2.63.1 (latest) down to version 2.7.1, with links to detailed documentation for each."],["The exception class extends `FlowController.FlowControlException` and includes a constructor that takes a `long` parameter representing the `currentMaxElementCount`."],["The class provides methods to get the current maximum batch element count (`getCurrentMaxBatchElementCount`) and to represent the object as a string (`toString`), as well as inheriting many methods from `Object` and `Throwable`."],["The exception is thrown when the maximum number of outstanding in-memory elements has been reached, and is used to signal when client side flow control is being enforced."]]],[]]
