Voiding Contest outcomes due to irregular lines

I completely understand that, for example, an over/under line that was typically at 8 and then went to 11.5, that taking the UNDER on an UNDER outcome (ie 4-2 final) should be voided, as you're being given a line that gives you an unfair advantage over the line most are receiving. 

That being said, if the line is 8 throughout and then jumps to 11.5 and you take the OVER, and the outcome is an OVER (ie 10-6 final), it's an unfair advantage for you, and you shouldn't have the selection voided, especially considering I didn't hunt or wait for this line, I just happened to make the selection just prior to game time. I actually waited to see if it would reset to the actual line for as long as I could.

I'm referring to the 7/1 Pittsburgh/Philadelphia MLB game where the outcome was 10-6. I chose the Over, and it was voided.

As a side note, when the freak are these line irregularities going to be resolved??? It's been well over a month, are your developers that incompetent???

Thanks in advance for your reply Covers. This is really creating a wrinkle in the contests (especially Streak Survivor) that puts us at a disadvantage when it's already a difficult situation (stringing together 17+ wins).

Actually, never mind on the first part of this thread, because although it shows in the popup that the selection was voided, I was still given credit for the selection, imo, appropriately and correctly, and I had the clear disadvantage.

But I'd still love to hear a response to the 2nd part, so I'll cut & paste it: 

Hello,

This is an issue with the lines we receive from the sportsbook, for whatever reason they are giving us incorrect lines for a short period of time, that revert back to the correct line. This is causing our contests to change to the incorrect line until they revert back, and in come cases a bit after this happens. We are working with them to fix this.

We will continue to void these lines that never actually existed as they come up and will keep working on the feeds.

@Flynt

That is such a cop-out, you didn't even address the question of why this is taking so long? Is it because you don't know???

Because they clearly are incompetent. You should have a checks&balances system in place to filter out the incorrect lines, based on the jump from the previous line. If the vig is too high/low, or the jump is too suspect, flag it, don't display it, and report it to the DB administrator to decide whether it is truly incorrect. Or utliize one of any number of other line services out there as your reliability back-up. Add the filter as a Chain of Responsibility Design pattern, that's my strong suggestion (to the developers).

Why on earth are your developers going about this problem the wrong way. You should never allow your system to be compromised by an outside 3rd-party service. This is an elementary computer science concept. Your developers are incompetent

@Flynt

 I apologize for making it sound like a personal attack on you or the developers. 

Bottom line:

This is a basic systems design issue—your current approach leaves you exposed to third-party failures. You need to have an executive at a higher level read the important parts here and understand that there's a fundamental issue with your development team, with as many problems as you've had over the past couple of years. This website used to work so seemlessly.

Hello,

I have shared this with our developers so they can prioritize a fix. In the meantime I will continue to void any incorrect lines that happen, as well stay on top of it to avoid it being available for too long.