2017-06-07: Service disruption

[rkulagow]

2017-06-14 @ 6:28P / 23:28 UTC

We are continuing to increase the data available. These are the items which should cause you to open a ticket at the Schedules Direct website through the "Lineup Support" function:

- missing station from the lineup
- station exists in the lineup, but is returning no data for the schedule
- severely truncated schedule (< 7 days)
- many instances of "To Be Announced" in the schedule

[rkulagow]

2017-06-16 @ 1:10P / 16:10 UTC

We have found an issue with some responses from our upstream; stations which are valid aren't returning data and are delaying processing because the null response is different than previous null responses, so our code was in an infinite retry loop. Code has been added to break out of the loop and we have notified our upstream of the stations which are causing the problem.

We will be increasing our upstream fetch quantity later today to restore 14+ days of schedule.

[rkulagow]

2016-06-21 @ 9:24A / 14:24 UTC

At this time we have had multiple days of uneventful schedule updates and will close this thread. If you are in the US / Canada, there should be at least 14 days of schedule. If you are outside of US/Canada, you should have at least 7 days of schedule data.

[rkulagow]

An update at our upstream had a side-effect of causing their image formation queries to bypass cache and generate heavy loads during high traffic hours.