max-response-delay in ARM examples is often equal to heartbeat-delay which we consider as wrong
We recommend the max-response-delay be a multiple of heartbeat-delay, yet in our HA example config snippets in the ARM they are frequently the same, customers are following the examples not the text.
max-response-delay - specifies a duration in milliseconds since the last successful communication with the partner, after which the server assumes that communication with the partner is interrupted. This duration should be greater than the heartbeat-delay. Usually it is greater than the duration of multiple heartbeat-delay values. When the server detects that communication is interrupted, it may transition to the partner-down state (when max-unacked-clients is 0) or trigger the failure-detection procedure using the values of the two parameters below. The default value of this parameter is 60000 ms.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information