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\u003eThe webpage documents the \u003ccode\u003eFlowController.LimitExceededBehavior\u003c/code\u003e enum within the \u003ccode\u003ecom.google.api.gax.batching\u003c/code\u003e package, detailing how the \u003ccode\u003eFlowController\u003c/code\u003e manages situations where flow control limits are reached across multiple versions.\u003c/p\u003e\n"],["\u003cp\u003eVersion 2.63.1 is the latest version of the documented \u003ccode\u003eFlowController.LimitExceededBehavior\u003c/code\u003e, while multiple other versions, down to 2.7.1, are also accessible for historical reference and comparison.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eFlowController.LimitExceededBehavior\u003c/code\u003e enum offers three static fields: \u003ccode\u003eBlock\u003c/code\u003e, \u003ccode\u003eIgnore\u003c/code\u003e, and \u003ccode\u003eThrowException\u003c/code\u003e, each representing a different way to handle flow control limit breaches.\u003c/p\u003e\n"],["\u003cp\u003eInherited members and static methods from the \u003ccode\u003eEnum\u003c/code\u003e and \u003ccode\u003eObject\u003c/code\u003e classes are also listed for \u003ccode\u003eFlowController.LimitExceededBehavior\u003c/code\u003e, providing a comprehensive overview of its capabilities.\u003c/p\u003e\n"]]],[],null,[]]
