Browsing when MaxNodesPerBrowse options are specified

[gtaylor1981]

When browsing, our client sees errors like "The request could not be processed because it specified too many operations."
We think this is caused by a server is specifying a lower value in "MaxNodesPerBrowse" (or similar) in its operation limits.
To browse, we call node.browseNodes(options).
The options are: BrowseOptions.builder().setBrowseDirection(BrowseDirection.Forward).setNodeClassMask(Set.of(NodeClass.Variable, NodeClass.Object, NodeClass.View)).build()

We saw setMaxReferencesPerNode() options, but setting this did not make a difference, and would have prevented us from seeing all nodes.
Can we somehow reduce the number of nodes made by our browseNodes() call, while still being able to access all data?

[kevinherron]

UaNode::browseNodes only ever specifies 1 Node to browse (itself), so perhaps it's one of the follow up calls (reading attributes maybe?) that is eliciting this error from the server.

Can you connect to this server without security enabled and get a Wireshark capture while this happens?