I wish there was a way to tell it to try again.Man, I’m pretty bummed, no movement since my failed 2.6.0 yesterday.
You’re not EA right?Just installed 2.7.3. It scheduled 30 minutes of down time but it took less than 10. Appears to be the same track as early access folks
That would be nice. Do we know how long the system waits after a failed install before it tries again?I wish there was a way to tell it to try again.
I am not early access. 2.6, 2.7.1 were one day to the next. 2.7.2 was four days after, but I didn't really drive in that time. 2.7.3 is 3 days after, and I drove every day intentionally.You’re not EA right?
How long between all the updates?
Seemed like it was a day or two later....That would be nice. Do we know how long the system waits after a failed install before it tries again?
I was only two days behind you on 2.6.0 and 2.7.1 but haven't seen anything for 2.7.2... I was hopeful as I drove 350 miles today...Just installed 2.7.3. It scheduled 30 minutes of down time but it took less than 10. Appears to be the same track as early access folks
When you say 'queued', are you referring to info you got from a widget/scraping ford.com?2.7.1 installed! Same way as yesterday. Queued, went for a drive and status changed to pending. Grabbed dinner and on the drive back the check mark showed up!
![]()
Ya. I pull it in via a shortcut. It says “request_delivery_queued”. Then it will go to a downloading status, then pending, then success.When you say 'queued', are you referring to info you got from a widget/scraping ford.com?