So, we never had this issue until the last two releases of Field Maps. Previous versions of Field Maps worked fine and so does Collector. I logged the bug and apparently it was "fixed" and yet I was still encountering the same issue.
Through some testing, I realized that we had attribute rules which were being calculated based on their spatial relationship with other features. Here's the kicker, we didn't have those other features published in our services used in Field Maps. I recalled that we had this initial issue with Pro when we first moved to the UN last year. And we fixed that by publishing the UN service with that extra feature. So in the end, the fix was to publish the extra features which are used to calculate the attribute rules all in the same service. Or check the 3rd Party Application option.
I guess we were probably experiencing the issue all along but Collector and earlier versions of Field Maps never picked up on this issue until the last 2 releases.