I have a survey published using Survey123 connect. I have several required fields, but they have relevant constraints. For example, if someone has a crossing type of "bridge adquate", the field is not required. All else, it is required. This works just fine in the mobile application, but, in the browser, if I select this crossing type, it still throws errors because I haven't filled in the required fields.
Apologies for the delay. I'm not able to reproduce the behavior you are describing with a simple form. Could you open a support ticket with Esri to determine what in your form design is leading to this issue?