@timshuwy With the transition to monthly CI/CD releases, is it already possible or planned to be possible to refresh the pilot environment from the live environment through CMP when the versions of the two environments differ by one monthly update (pilot 2026.104 / live 2026.103)? Since these monthly updates are intended to be non-breaking updates, that should require no database schema changes; therefore, in theory, should not pose any issues. The reason for this question is with the increased frequency of the smaller monthly updates, (which I see as a positive), it would be beneficial to be able to keep pilot on the latest monthly release, keep live one release behind, and still be able to refresh pilot at any time. I would love to update my pilot environment right now to 2026.103 but I fear needing to refresh pilot from live before I am able to update live and being stuck.
You can do that now. 
when you have pilot at a different version and you try to do a refresh from live it will warn you and then it will do the refresh, you just then have to trigger the update/update to align the pilot db and the pilot app.
See @BenWheeldon’s Answer.
Cool!
If you try to do the refresh and the versions are too far apart, will it prevent it or just give the same warning? In other words, do I have to know if the db versions are compatible? My pilot and live environments are currently both at 12.2.100.9. If I upgrade pilot to 2026.103, will I still be able to refresh pilot from live? My apologies for all of the questions but I want to check out 2026.103 and am afraid of breaking pilot.
Thanks!
I have not personally done it for a monthly continuous track release. However it worked for major releases such as live at 2025.2 and pilot at 2026.100 so I don’t see why not.
I ran ours in Pilot and you’d be surprised…
Several formerly working dashboard now aren’t. They can’t even be opened in App Studio. There’s a long list of errors in the conversions logs, which run at the tail end of the update.
I was going to do the monthly update to 2026.103 on Pilot today since it is going to happen automatically next tuesday, and I found this Important message that now has me hesitating. I also have to note that the old “update” button doesn’t have any versions to upgrade to, listed, but this monthly one has 103 and 104.
Has anyone checked the “Important” checkbox and what is it like on the otherside? I am worried about not being able to get fixes anymore.
They are continuing to release dot releases against 2026.100 that contain fixes. Personally I wouldn’t do it, being Epicor’s beta testers 1-2x a year is bad enough. Every month?
Isn’t .9 the latest and last?
Nope, they are still releasing dot releases every 2 weeks. They do not make every dot available for cloud. Cloud will be getting .14 in a couple of weeks. Its all on the epicweb schedule. Sign In
And to save you from MFA:
oh looks like MT/Express Americas and US Gov Cloud Customers have the .14 and .16 route
There are two different schedules on that page. One is for CICD (public cloud/non-flex only) and a separate schedule everyone else.
Good luck 
I think enough people opened tickets from that check box that they decided to remove it. I know that we had several tickets that were waiting on fixes and it took a few days to get responses. We were told that Public Cloud is going 2026.103 for the next update and will move the monthly cadence. Currently our Pilot Env is moved over and we are holding off as long possibly can to have our Prod environment move over because of some issue we found in the 103 release.
It doesn’t look to me like the customers on cadence have an option to stay on Maintenance Track.
Continuous Track vs Maintenance Track
The Continuous Track is for public cloud customers, while the Maintenance Track is for on-premises, Enterprise Cloud, US Gov Cloud, Flex, and Life Sciences customers.
The Continuous Track delivers one annual baseline release each year, plus monthly releases that can include new features, enhancements, fixes, and security-related updates. The Maintenance Track also starts with one annual baseline release, but after that it receives minor updates or patches rather than monthly feature releases. In simple terms: Continuous Track = annual baseline releases + monthly feature releases. Maintenance Track = annual basline releases + minor patch updates.
I also noticed that once upgraded to the monthly release, you don’t have the option to switch it back to minor patch updates (or Maintenance Track).
That makes sense though, the only way I could understand Epicor allowing you back would be on the next major release when in theory, both would be equal in terms of features. Because the ‘rolling release’ is pushing out changes to features I expect it would be difficult to have a customer revert back, probably not impossible but something I can understand Epicor having 0 desire to support.