My team and I received the same email. Unfortunately i am in a meeting and haven’t been able to read it as thoroughly as I would like to.
Didn’t get one of those emails so I guess we’re still on the clock.
That email also says your (or your customers) Linux migration WILL be done this weekend as scheduled…so you’re only suffering half as much.
I know we have discovered a lot of EF Core issues (over 100). We have fixed those in Pilot, but not in our Live DB yet. We were going to do that this week. I am guessing this only was sent to people who will have EF Core issues, and since our fix isn’t in place yet, we were included.
Don’t know…we’re still scrambling to get all of our testing done. A lot of late triage work - some Linux related, some not. We can’t even test fully until Wednesday as it is - 2026.100.7 has two hot fixes (quote worksheet, customer shipment entry).
Trying to keep a level head this week but it’s getting hard…
The action part of the email seems to be missing words: If you prefer to remain on cadence and receive your Production upgrade this weekend, July 10-12, an EpicCare case will be created for you by Monday, July 6, on this topic. Update this case directly to stay on cadence. The case will have the same subject as the email.
This makes it sounds like support is creating the case for me, but i don’t see one in EpicCare yet.
I just checked and I do not see a case either.
How confusing and urgent can you get - we have been preparing for a year and now i get one hour to STOP them for moving the date from this weekend to October?
DaveO
Why would you stop them.
what they are trying to say is that there is a support case already created for you to defer your upgrade, but if you want to stay on cadence, you need to update this case. The case’s subject will be the same as the email.
Note, if you dont see a case, and you want to stay on cadence, you should enter a case to make your desires known.
The problem was not detected in the customizations for all customers. If you didnt get the email, it means that your customizations did not have a pattern that EF Core would dislike.
Note that this is not a “compile” problem… the programs would compile, but for some reason, EF Core dislikes some of your customizations, and throws errors at runtime. We were able to detect those errors, and therefore were able to filter out those customers who had the challenge.
Mr. Tim: Thank you for the feedback.
I do not see a ticket for the one customer that I am pretty sure this relates to.
There is no case number that i have found.
Also, I have corrected the EF Problems in Pilot for most - is this message looking at our Live?
Am i reading this wrong or do I only have until the end of today i.e. now to either respond to a case that does not exist, or create a new case?
DaveO
Thanks for the clarification…we don’t have a lot of customizations, mostly BPMs/functions, still working our way through final checks. Not crazy about only getting two days to test 2026.100.7 when it gets loaded tonight…it is what it is. Do the best we can under the circumstances.
EDIT - aaaaand we just got what appears to be our first Pilot EFCore issue…AP positive pay. Happy Tuesday y’all! 
I appreciate Epicor’s proactive approach to this Tim. Please thank the team/person(s) who decided it was worthwhile to fully investigate this.
I’m glad they are doing this we’ve had too many gremlins in 26.100 to be comfortable. To say I was not nervous about this upgrade would be a lie.
I did see a case that was created for one customer this morning - as of last night there was no case created.
I still am unclear about which environment they are referring to. Is the report based on Live or Pilot or Third?
DaveO
Just kidding, but Epicor, if you are listening…
These emails need to be much more detailed.
How, where, what, when, and why.
I got the email yesterday also. I saw this morning that there was a ticket in EpicCare regarding the email. I asked if the scan was only done on our Pilot database or LIVE database. Also let them know we had been making changes in Pilot so we could test things before we put them into LIVE. Will let you know what their response is.
I did ask them to delay our upgrade. I know I said I really didn’t want to do a self upgrade again but if we get everything fixed in the next few weeks or so, we may just try it on LIVE.
Good luck everyone who is still moving forward with the upgrade this weekend!! I know the stress you all are feeling 
I’ve found that if you stare at them long enough, the information is almost always extractable. Sometimes you have to put together multiple notifications and backsolve into an implied meta-notification. Doing at least a Puzzled Pint once in a while helps.
So it often goes for notifications written by developers / engineers, who as a group are unfortunately prone to writing duck konundrums. If Linux is in the blue chair, the environment wearing a hat is to the left of someone who skipped breakfast, etc. etc.
Same for us, I haven’t applied to our PROD the EF Core issues found and corrected in Pilot. But we’re happy for the delay to get more testing in.
That is really short are there issues .7 is supposed to address for you?
Two in particular - the Quote Worksheet bug that other have brought up, plus Customer Shipment Entry is off the rails (shows all sites instead of just the one you’re in - basically lost user/site level security and filtering).
"