Something was pushed over the weekend which triggered the Pilot desktop client to attempt updating itself again, except the update is a desktop rollback without a server rollback.
We’re getting a browser-only Pilot preview three months early. Power Tools .14 is working at the moment and it’s just Pilot so that’s alright. Would get interesting if a Live update did this before the end-of-desktop deadline if we hadn’t already made the move.
I’ve had this happen on a non-prod before, cloud team can fix it by editing .sysconfig or something, it was a quick fix. Some script bailed out and set the wrong setting somewhere.
Good luck I hope all works out well.
As long as it’s Pilot I’m honestly appreciating the unexpected functionality testing. Development attention being prioritized away from the desktop client to the browser may increase the odds of desktop snafu’s in the next three months.
All went well. I can tell everyone that at one point, our company has the latest version of Epicor in Production. 
On the weekend, our project manager able to organise resources to fix the client update issue, regen model issue and ECM connectivity issue. All sorted on Sunday. Really thank Epicor for jumping in and solve those issues.
Good to hear!
New thread for 2025.2.16? lol
To be fair, this is the farthest ahead in notifications we’ve had in a long time. I took a double take at the dates for the PILOT and PROD notifications.
Hopefully the dark days of last minute emergency notifications are over.
Just got it too…so why would we upgrade to 2025.2.10 when all the rage was about getting to 2025.2.14 a week or two ago?
EDIT - now just got ANOTHER one about Flex 2 going live on 2025.2.10 in that same 3/20 weekend window. So what the heck did we need 2025.2.14 in Pilot for???
John, are you not already on 2025.2.10?
I can confirm that we did get this email and our production environment is currently on 2025.2.10.
Perhaps they meant to 2025.2.14?
Nope…2025.1.11 live, 2025.2.14 pilot.
We were one of the customers who lost Pilot functionality due to the Linux situation. Supposed to go live in February, given the option to defer to March. At this point I don’t know WHAT we’re considered…on flex-cadence?
Yep, we are also already on 2025.2.10 in Live. I was under the impression this was being held off until 2025.2.16 in April. I guess I am not sure what to believe at this point .
I got the same email and we are already on 2025.2.10. This makes zero sense. I put a priority ticket in Tech support. Don’t know what is happening at Epicor but I am really getting concerned about them.
@utaylor who is the “from” on this email. Feel fre to DM me that.
How can Epicor expect MFG companies to go all weekend without ERP? I don’t understand that logic. They post these weekend long maintenance windows all the time. Blows my mind.
Anyway. That’s all I’m going to say. Peace spoken.
We’re lucky - we’re 5-day and 2-shift (for the most part) so Fridays at 11p ET are essentially our shutdown time…but what are 24/7/365 shops supposed to do?
This upgrade does not show up on the Epicor Cloud Status page.
I did just get another email showing the exact same upgrade except it is for Flex Option #2 customers.
Hoping the first email was a mistake.
Crazy!!!
Yeah I just reached out to our consultants about it too…this stuff just makes zero sense whatsoever. If they came back and said “oops, this was a scheduled email that was queued up weeks ago”…that might make sense.
