NextEnd Readiness

[mvallevand]

Yes the new Schedules Direct name was the problem. I just haven't got around to making the build sorry.

Martin

[jcole998]

Good catch, snagglewest...

[mvallevand]

Although I haven't tried this against running races, could you see how this works out and let me know. I have to do another update for Formula One which changed to Formula 1 for next week.

Sorry for the delay I moved PC's a few months ago, and forgot to transport over my NSIS installer components so had to figure that out too.

Martin

[jcole998]

OK, Martin. Will let you know how it works.

[jcole998]

Nailed it, Martin! Log shows that yesterday's Phoenix race was monitored quite nicely with, on this occasion, no need to extend.

Many thanks.

[mvallevand]

Great thanks for the feedback.

Martin

[jcole998]

The NASCAR Charlotte race ran until well after its scheduled stop time of 10:30pm. The recording was not extended though I believe that it should have been and stopped with 80 laps to go. Coverage began at 6pm on the 26th.

Would you take a look?

Thanks...JohnC

[mvallevand]

When NextEnd checked at 22:11 ESPN still showed the status as not started so NextEnd won't attempt to do anything when it figures the API is not behaving. The API web site isn't great with rain delays and restarts.

Martin

[jcole998]

OK, thanks, but I have to ask about the status being shown in the log at 22:11:07: [Title=NASCAR Racing, Status=Start Delay, IsValid=True, IsActive=False, IsComplete=False, IsError=False, ]

Looks to me like the event was still in progress because IsComplete is false and IsValid is true. "Start Delay" could easily mean a red flag for rain or crash cleanup. "IsActive" is admittedly very vague but I could mean "not under green."

Does Nextend logic need to be tweaked a little? Anything I can do to help?

JohnC

[mvallevand]

Start delay is what I have the server respond when the API tells me the race is not started when the check is made.

Martin