Waits until the request can be made without exceeding the limit.
This might be appropriate in batch-processing, where latencies of individual requests are
not important.
Ignore
Disables flow-control.
This is provided mainly for debugging and not recommended for production use. Having too
many requests in-flight might cause RPCs to fail due to congested network or the computer to
run out of memory due to excessive buffering, etc.
ThrowException
Throws MaxOutstandingElementCountReachedException or MaxOutstandingRequestBytesReachedException.
This might be appropriate in interactive scenarios. For example, a web server might catch
these exceptions and report to the user that the system is overloaded and that the user could
try again later. It could also be useful in applications that implement custom rate-limiting
logic.
[[["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."],[[["\u003cp\u003eThis webpage provides documentation for the \u003ccode\u003eFlowController.LimitExceededBehavior\u003c/code\u003e enum in the Google API Client Library for Java (gax), detailing its usage across multiple versions, ranging from 2.7.1 to 2.63.1 (latest).\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eFlowController.LimitExceededBehavior\u003c/code\u003e enum specifies the actions taken by \u003ccode\u003eFlowController\u003c/code\u003e when flow control limits are exceeded, including \u003ccode\u003eBlock\u003c/code\u003e, \u003ccode\u003eIgnore\u003c/code\u003e, and \u003ccode\u003eThrowException\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eBlock\u003c/code\u003e behavior will wait until a request can be made without going over the set limit, making it more suitable for batch-processing.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eIgnore\u003c/code\u003e is mainly for debugging and disables flow-control, which can lead to RPC failures.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eThrowException\u003c/code\u003e is suitable for interactive situations, such as a server reporting that the system is overloaded, or for custom rate-limiting logic, and throws either \u003ccode\u003eMaxOutstandingElementCountReachedException\u003c/code\u003e or \u003ccode\u003eMaxOutstandingRequestBytesReachedException\u003c/code\u003e accordingly.\u003c/p\u003e\n"]]],[],null,[]]
