Our system is Cloud on-cadence in the US. Based on these still-current posts I have been planning for the upgrade to 2024.1 in Live on July 19.
But just got a status email message (7/4/24) that says the production upgrade will occur July 13, and there is an Epicare home page banner announcement that also has the July 13 date.
So, which date should I believe?
I don’t understand why they continue to send notifications that are just plain wrong. Every time it happens I open a support case and ask for confirmation of the correct info. I am pretty sure its still the 19th but opened a case when I got that email anyway to get it in writing.
I just saw all of this same thing. Put me in a small panic as our Pilot environment is due to be upgraded this coming Tuesday. How can they move the LIVE upgrade up one week and then only give us 2 days to test?? Does not seem right. I also put in a case with Epicor. Very frustrating!!!
Here is a direct quote from the support case I raised:
“The production upgrade for US customers is on the 19th.
The Pilot upgrade will be on the 9th.”
That is a fine answer about Production, assuming they are referring to July 19. But our Pilot upgrade WAS actually on the June 18. Did they postpone some Pilot upgrades from June to July 9 @JillMetalworks? If so, that is not very considerate.
This is my first upgrade since transitioning to Cloud in February 2024. Are the dates and alerts always this chaotic?
The .8 update for Pilot is on the 9th.
They upgraded Pilot to 2024.1.5 on June 18th. They are upgrading Pilot to 2024.1.8 on June 9th. Then they are upgrading LIVE to 2024.1.8 (which will include the 2024.1.5 upgrade) on July 19th.
I got the same response from Tech support as you did.
And yes the dates and alerts can be chaotic from time to time. I have always found that posting on this forum and putting a ticket into EpicCare always solves any questions you may have. Also you can contact your CAM.
Good luck with your first upgrade. The first one is the most nerve racking. After that you will know what to expect and have your process down pat. Just make sure you have a good upgrade script to reference and update after each upgrade.
How much testing do you do for .X upgrades? I thought these were usually minor and didn’t really need a complete testing plan. Can I just read the release notes and see if anything looks obvious? Do you have different test plans for 2024.X vs .X upgrades?
We do full tests for major.MINOR.point
We usually just pray for major.minor.POINT
Note: That’s not the terminology Epicor uses, I just used it for demonstration purposes.
Not surprised they have their own terminology for prayer but didn’t see it coming
Hi Andrew,
For minor upgrades, I just go through the basics. I check our EDI process, check out our Customizations, check out some of our key reports, and just things that I know can be compromised sometimes from an upgrade.
For major upgrades, like the one coming up July 20th, I go through the whole process of Quote to Cash. I have our Order Entry people enter in some orders for key Customers that we watch out for, test out the EDI process, go through the whole scheduling and MES processes, the whole shipping process and make sure that invoicing still is functional. I also make sure to double check certain forms and customizations.
For both upgrades I run the verification of Customizations, verification of personlizations, recompile BPMs, double check our configurators, redeploy all Dashboards and run a full MRP.
You will figure out your own list as you go through each upgrade. Keep good notes and follow your script each and every time. It really does help.
I received the same email announcement…
But when I went to EpicCare (for a completely different reason)… there they have it posted as:
I think the issue was that the email they sent out didn’t have the “G” for Govt. Cloud.
Either that… or they fixed it after they sent out the alert and realized they posted it to the wrong group.
Using @klincecum terms: Major.Minor.Point We do largely the same, full tests on both Major and Minor updates. Point updates we do some spot testing based on what we find in the release notes.
I also got the 2 confusing emails on the dates last week so I filed an EpicCare ticket today with Cloud Ops to clarify. This is how that went. I may have kindled a little dumpster fire 
to prove a point in the process. For those of you paying attention to the dialog below I think you will find there is still confusion in their answers. I get it everyone of us makes mistakes, including me, but still… Enjoy! 
Epicor Support: For regions that have already had their Production environment upgraded to 11.3.100.5 - we will be updating their system from 11.2.300.5 to 11.2.300.8 on 7/13. In your case - your Production environment is still at 11.2.400.11 - so no action or update will take place on 7/13. Your major Migration to 11.2…300.8 will take place on 7/19
Epicor Support: State: Suggested Resolution
Me: Ok can you please translate your 11.x numbers to 2023.x or 2024.x version numbers please. I realize Epicor uses 2 different numbering schemes but that makes it HIGHLY confusing for us IT admins and users. I am still hopeful Epicor will 1 day adopt a single version numbering scheme.
Epicor Support: Sorry for the confusion Chris. Your Live system is currently on 2023.2.11 and will be upgraded to 2024.1.8 on 7/19-20. You will be getting an update on 7/13 - those are for the regions already on 2024.1 in Production.
Epicor Support: State: Suggested Resolution
And Scene!
This is the current message I am receiving for 2024.1 in LIVE:
Aug-23, 7:00pm MST
Kinetic - Americas on cadence and Flex customers are scheduled for the 2024.1.10 major Production upgrade:
From: Friday, August 23, 10:00 PM Local Datacenter Time
To: Sunday, August 25, 9:00 AM Local Datacenter Time
Your Production system will be unavailable for several hours during this time. Pilot environment testing is required before the Production upgrade.
An all clear message will be posted when the update has been completed. Please plan accordingly.
ENVIRONMENT
Production
Epicor Released 2024.1 in May 2024 right before Insights in Nashville. Yet the LIVE environments in Public Cloud are still showing 2023.2 over 3 Months Later!!
Our LIVE Production Public Cloud environment current version: 11.2.400 =2023.2!
We are Paying for Public Cloud to be Automatically Upgraded Twice a Year - April/May and September/October and we are NOT FLEX as those windows align with our business operations. If the Upgrade windows are Pushed then we may be Forced to PAY for the FLEX option.
Epicor needs to Remain on their Cadence.
We are in the process of Manually migrating (Re-implementing) from On Premise to Public Cloud and we need to Refresh Live over Pilot to enable the various Testing cycles as we build our system. This Version Mis-Match is majorly affecting our GO Live at end of year!
Epicor doesn’t guarantee those dates, and quite a bit has happened this year.
Agreed… but I also see his pain point.
Because he isn’t FLEX, our PILOT was upgraded to 2024.1 on June 20th (if memory serves) with LIVE scheduled for July 21st. So, one month we should have to deal with a Version Mismatch.
The mismatch can have a huge impact depending on how you utilize Pilot. Not being able to refresh you Pilot with Live data because your Pilot is on a newer version should be a short-term issue. But pushing that major update another MONTH means another MONTH of version mismatch.
Frustratingly (in my case)… in the LAST cycle of 2023 major upgrades (which was my first dealings with Epicor rollouts), Epicor updated my Pilot with Live automatically (without me requesting it) prior to updating Pilot. This time around, I assumed I didn’t have to request it, and they DIDN’T update Pilot prior to pushing the 2024.1 update. So, my Pilot data hasn’t been updated since February (the last time I requested it), and I’m locked out from doing so until Live catches up version-wise.
Totally feel you, @bnestel . Can’t do anything about it… but I feel you.
![When the World Lets You Be a Reclusive Introvert… and You're Still Not Happy | [One Fifty]](https://nomorethan150.wordpress.com/wp-content/uploads/2018/07/giphy1.gif)
Yes, me as well.
Frustration sucks, no matter what it is. We’ve all been there.
Just ask them to upgrade you, no need to wait until the end of August. We did ours last week.
Didn’t know this was an option which has me thinking but is there any down side to not following Cadence and going early?
