Yes, so according to this, your update failed. I assume the reason you did not get the error from the client about the MXF file being too old was because you did have a successful update prior to this but it was less than 24 hours ago (or whatever threshold is used before reporting an error, it may be a bit less than 24 hours, I don't remember what Gary said is used).jwk wrote: ↑Sat Jul 10, 2021 8:11 pm [7/9/2021 3:05:39 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.
[7/9/2021 3:10:39 AM] [ERROR] Failed to complete request. Exiting
[7/9/2021 3:10:39 AM] [ERROR] Did not receive a response from Schedules Direct for 147 station's daily schedules. (0:00:10:00.0502691)
[7/9/2021 3:10:39 AM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[7/9/2021 3:10:39 AM] [ERROR] Failed to create MXF file. Exiting.
EDIT: I checked the source code and if the MXF file is older than 23 hours it will log the ERROR message about it being out of date.