No recent schedule data for USA-OTA-40324

[dcheckoway]

Hello! First off, thanks for a very well documented API. I'm a brand new user, just tinkering for now with my own PVR (if it amounts to anything I'll share it). Anyway...

I've been walking through the steps outlined in https://github.com/SchedulesDirect/JSON ... I-20140530 and everything worked great up until the point where I queried for schedule data. Looks like `/20141201/lineups/USA-OTA-40324` was last updated `2016-05-08T22:45:33Z`.

I haven't paid yet, still a trial user (username "dcheckoway" registered earlier today). Am I missing something obvious?

Code: Select all

curl -s -X POST -d '[{"stationID": "47303"}]' -H 'token: ...' 'https://json.schedulesdirect.org/20141201/schedules' | jq .
[
  {
    "stationID": "47303",
    "serverID": "20141201.web.2",
    "code": 7020,
    "response": "SCHEDULE_RANGE_EXCEEDED",
    "minDate": null,
    "maxDate": null,
    "requestedDate": "2016-05-22",
    "message": "Date requested (2016-05-22) not within  ->  for stationID 47303."
  }
]

Code: Select all

curl -s -X POST -d '[{"stationID": "47303"}]' -H 'token: ...' 'https://json.schedulesdirect.org/20141201/schedules/md5' | jq .
{
  "47303": []
}

Code: Select all

curl -s -H 'token: ...' 'https://json.schedulesdirect.org/20141201/lineups/USA-OTA-40324' | jq -r .metadata.modified
2016-05-08T22:45:33Z

[rkulagow]

What happens when you try it now?

[dcheckoway]

@rkulagow same thing still happens.

[rkulagow]

OK, let me investigate further.

[dcheckoway]

@rkulagow it's working great now. Thanks for whatever you fixed!

[rkulagow]

I use a ping/pong scheme for the database, and "ping" has issues, so now we're on "pong".

[rmeden]

oh dear... no we're out of options!

[gtb]

oh dear... no we're out of options!

There is still plink, plop, plunk, and, when you need to use a much bigger hammer, and do not mind the need for professional cleaners, splat