Does Reach specify a retry policy when a participant's RPC call to the consensus network times out?
I'm building a Reach DApp with two participants (a deployer and an attacher) targeting Algorand, compiled with a recent Reach release. The generated frontend stubs in build/index.main.mjs handle all communication with the consensus network through the connector, and I have no user-facing configuration for transport behavior. My uncertainty: when a participan