Strange issue here. The setup: I have a map of parks that are classified and symbolized by the attribute field "Assigned." The field contains a domain, either "Assigned" or "Not Assigned." There is an internal and public facing version of the map. The Internal version draws on a service published to our federated server (Enterprise 10.8.1). Editing capabilities are enabled on the feature service, but the issue is that only some of the features within the feature class respond as expected to adjusting the "Assigned" field. As far as I can tell, there is nothing especially in common among the features with accept the edit and those that do not.
Some extra info, this issue has occurred in the past, when all of our services were run off an ArcGIS Server site and consumed in AGOL. (We've since updated to Portal). The same strange editing behavior occurs in both the web map and the webapp (see attached video clips). However, all the features in this feature class remain editable in an .mxd/.aprx. which tells me the issue is related to how they are being consumed on the web. Our City has many different feature classes and services consumed in a variety of web locations, and as far as I can tell this is the only one exhibiting this behavior.
Any ideas as to why some features in the feature class would not be accepting the edit via dropdown domain?