Hi Joel,
We had looked into this issue and found out it's a regression issue with 3.11 version of the web application and had logged an internal issue to fix this in the next release.
If you see a need to track this fix, I would encourage you to submit this issue as a bug via Esri Support. Our Support team will assign an official bug number for your records. This number can be used to search for and subscribe to the bug on the Esri Support site. If the issue is reported by other customers it will be attached to the same bug report, which helps us assess the impact of the issue and prioritize it accordingly.
Thanks for reporting this.