NextToArrive API (Half) Broken

[Aaron Ogle]

Just a heads up to the folks at SEPTA that I'm seeing intermittent but regular issues today with the NextToArrive API endpoint. Approximately half of the calls that I make to the server are return no results (but not throwing an error). I suspect that there is some load balancing happening and that one of the servers is not returning results correctly.

To recreate, reload this example call in a browsers several times in a row.

http://www3.septa.org/hackathon/NextToArrive/Airport%20Terminal%20B/Ardmore/10

[Joe Walsh]

I'm also seeing this (or a similar) issue. Half the time results will be returned with incorrect connections and no arrival times.

An example URL I'm seeing the issue on is:

https://www3.septa.org/hackathon/NextToArrive/Glenside/Jefferson%20Station/10

[Joe Walsh]

And an example of one of the broken responses:

 

[{"orig_train":"567","orig_line":"Lansdale\/Doylestown","orig_departure_time":" 5:10PM","orig_arrival_time":null,"orig_delay":"10 mins","term_train":"567","term_line":"Paoli\/Thorndale","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"10 mins","isdirect":"false"},{"orig_train":"4571","orig_line":"Warminster","orig_departure_time":" 5:35PM","orig_arrival_time":null,"orig_delay":"14 mins","term_train":"4571","term_line":"Paoli\/Thorndale","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"14 mins","isdirect":"false"},{"orig_train":"573","orig_line":"Lansdale\/Doylestown","orig_departure_time":" 5:54PM","orig_arrival_time":null,"orig_delay":"On time","term_train":"573","term_line":"Paoli\/Thorndale","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"On time","isdirect":"false"},{"orig_train":"6455","orig_line":"Warminster","orig_departure_time":" 5:56PM","orig_arrival_time":null,"orig_delay":"On time","term_train":"6455","term_line":"Airport","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"On time","isdirect":"false"},{"orig_train":"5265","orig_line":"Lansdale\/Doylestown","orig_departure_time":" 6:11PM","orig_arrival_time":null,"orig_delay":"On time","term_train":"5265","term_line":"Wilmington\/Newark","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"On time","isdirect":"false"},{"orig_train":"577","orig_line":"Lansdale\/Doylestown","orig_departure_time":" 6:37PM","orig_arrival_time":null,"orig_delay":"On time","term_train":"577","term_line":"Paoli\/Thorndale","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"On time","isdirect":"false"},{"orig_train":"461","orig_line":"Warminster","orig_departure_time":" 6:50PM","orig_arrival_time":null,"orig_delay":"On time","term_train":"461","term_line":"Airport","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"On time","isdirect":"false"},{"orig_train":"4269","orig_line":"Warminster","orig_departure_time":" 7:11PM","orig_arrival_time":null,"orig_delay":"On time","term_train":"4269","term_line":"Wilmington\/Newark","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"On time","isdirect":"false"},{"orig_train":"579","orig_line":"Lansdale\/Doylestown","orig_departure_time":" 7:17PM","orig_arrival_time":null,"orig_delay":"On time","term_train":"579","term_line":"Paoli\/Thorndale","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"On time","isdirect":"false"},{"orig_train":"463","orig_line":"Warminster","orig_departure_time":" 7:23PM","orig_arrival_time":null,"orig_delay":"On time","term_train":"463","term_line":"Airport","term_depart_time":null,"term_arrival_time":null,"Connection":null,"term_delay":"On time","isdirect":"false"}]

[Greg Apessos]

Hello,

   Sorry for the delay, but I believe I fixed the issue a few days ago but haven't had a chance to update everyone.  Could you let me know if data looks good on your end? 

-Greg

On Monday, August 28, 2017 at 1:57:42 PM UTC-4, Aaron O. wrote:

[Joe Walsh]

Looks good on my end. Thanks!