Just another story: failed for no reason, why?

[Joshy-Poo]

I've been having this issue where I'll get in the car and get a timed mission, I'll be driving to the destination and still have plenty of time on the clock, then suddenly will get the notification that I've failed the mission. This will also happen to the other missions, such as where you've got to kill the enemies on your tail, I'll be killin em and suddenly, congratulations you've failed the mission. I have no idea what's causing this and hell sometimes it doesn't even tell me that I've got enemies on my tail, I need to get it said place in said time, or even that I need to deliver the car in preem condition, It'll just fail me for no reason at all. Don't know if new update completely broke these missions as this wasn't happening before for me. Also while I'm at it, Sandevistan will not work while Muamor "El Caption" Reyes is on the call, an it's annoying.

[JokersUAV]

Happens to me too came here looking for answers. 2:50 to go and sorry Choo better luck next time. Absolutely nothing wrong. tested 5 times fail all 5 times. Some were dont bang it up some were timed and some were shot outs all fail

[Dweller Beyond the Threshold]

yeah I believe this could be a bug introduced by 2.01. It worked fine before in 2.0 but 90% of the time the gig would just fail after starting it for a minute.
It's weird though because not that many people seem to have encountered it when I asked around, so I thought maybe it was caused by one of my mods. Do you guys use mods too?

[azogthedefiler25]

This has been happening to me as well. I had it happen before the 2.1 patch. The car delivery missions are always hit and miss. I don't miss doing them.

[Dweller Beyond the Threshold]

Originally posted by azogthedefiler25:

This has been happening to me as well. I had it happen before the 2.1 patch. The car delivery missions are always hit and miss. I don't miss doing them.

that's weird...I did a ton of these, enough to get 2 cars almost free with discount, yet I didn't get this weird bug a single time. It only started happening after 2.01 patch.
So yeah, honestly not sure if it's a vanilla bug or something else that's causing it because everyone's experience is so different.