I make schema modifications in my enterprise geodatbase, connected to SDE as the schema owner, in the Catalog pane of my Pro project.
The layers in the map of my Pro project are owned by the data owner, who has the add/edit/delete permissions for use in apps.
If I, for example, add a field to my feature class that is the data source for a layer in the map, that field will not appear in the layer properties or the map until I restart Pro.
Similarly for management properties, such as adding global IDs, setting versioning type, enabling editor tracking, etc.
The schema change will not propagate to the layer. And if I publish, the changes still are not detected.
I wonder if it has something to do with caching within the Pro client. I think that Pro caching some of the layers information to allow more performant responses in the client.
Interested to see what others say also.
Have you heard about this happening before?
I have assumed it to be some caching mechanism that is overstepping its boundaries.