We've been using SQL Server reporting services for many years, programmatically using the ReportingService2010 client generated from the 2010 endpoint. Users of our application can create and manage schedules and scheduled reports.
One of the calls our code uses is the standard GetScheduleProperties, which returns a Schedule object (as out param). The Schedule object contains a ScheduleDefinitition object which provides the details of the schedule definition, such as StartDateTime and EndDate.
Against SQL Server 2014 reporting services (and previous) this worked fine - the Schedule object came back properly populated. However, against SQL Server 2019 reporting services the ScheduleDefintion object comes back with '01/01/0001 00:00:00' as the StartDateTime property value.
Is this a bug or are we missing something? Note we haven't changed the code other than updating the service reference against the latest service.