Mismatched cached plan in SentryOne
These two stored procedures have the same object names but with different schema ID and object ID.
The cause of this results from dbo.GetPlanHashAndTimeForObject one of the input parameters of which is objectName instead of objectID in dbo.PerformanceAnalysisTraceCachedPlans
Obviously this is a bug. In our shop within the same database there are over 500 user stored procedures with the same name but different schemas.