Using Pro 3.1 and an up to date geodatabase, the overwrite web layer function results in an empty feature service. The data is a small (12 features/records) polyline feature class with attachments (3-6 .jpg files for each feature), and so it includes a table relationship.
Feature service was successfully published using Pro 2.8 approx. 4 weeks ago and successfully overwritten 2 weeks ago. A second overwrite then resulted in an empty service with unhelpful 'data error' message when viewing Data under Item Details in AGO. Tried publishing the feature class to a new feature service, again resulting in empty data. Upgraded Pro to 3.1, but both overwriting and publishing a new feature service result in empty services. In Pro, the feature class has only single symbology applied, and the only changes have been to the attached files and the field aliases.
What's especially confusing is that in AGO I can symbolize the empty feature service based on field values that can clearly be read and applied even though the attribute table is empty. The feature services are not publicly shared.
