We have ArcGIS Enterprise 10.9.1 and SQL Server 2017 enterprise geodatabase. There are several feature services published to the hosting server multi-machine site which are used by different sets of editors around the business. These aren't high traffic services so in order to save on server resources the services were set to use the shared instance pool (available if the service is published from Pro).
Editing is being carried out using either the Smart Editor widget in WAB app or via the Field Maps app. Access to maps and layers is being controlled by Portal groups and none of the content items are shared more widely than groups.
A user of one of the editable layers has noticed odd values appearing in the last edited column of the tracking data - in some cases their name is recorded against features that they know they have not edited and in a small number of cases the name of someone from outside their team has been recorded, despite that person not having access to the layer or map via Portal sharing. From what we can tell it appears that the attribute and/or geometry edits against that particular record are correct, just that the wrong name has gone into the last edited user field.
In one of the cases we can see that the user from outside the team was submitting a record in their own project in Field Maps at the same time (at least to the minute), but that's not always the case.
The only thing we can think of that is linking these users together is that they are all editing feature services that are running as shared instances on the same ArcGIS Server site. So we were wondering if there is some sort of cacheing or mix up of user names going on within the shared instance.
We've now set the feature service that was getting the incorrect tracking to be a dedicated instance and after 24 hours there don't appear to be any rogue editor names from outside the team. It may just be that the exact circumstances which caused the problem have not arisen again and there is no guarantee that the names it has recorded are necessarily correct (unless we specifically ask users to check after each edit).
Has anyone else ever experienced this issue when working with shared instances? There is nothing that I can see in the documentation which says they can't or shouldn't be used for feature access/editing but I think for the time being we will stick to dedicated instances for any editable services.
