Everyone make sure your resume is up to date.
Same hereā¦guess our servers had enough hamsters on the running wheel to keep them powered upā¦
Donāt go and jinx it now! 
Add it to the list of SaaS issues lately.
No all clear yet but our Epicor is back up.
Ok, the All Clear has been sent.
The incident affecting the availability of Kinetic for a subset of customers in the Americas region has been resolved. Our teams identified SQL blocking within the database environment as the cause of the disruption. Service has been restored, and monitoring has confirmed that the system is operating normally.
We apologize for the disruption and appreciate your patience while we
OK, now that it seems to be resolved, time to address the 
in the room.
This is the third outageā¦sorryā¦āincidentā in two weeksā¦694768 (7/24), 697144 (7/31), 698021 (today).
Wonāt speak for anyone else but itās starting to become very uncomfortableā¦you can only āremediateā so many times before itās regarded as a chronic problem.
So Iāll askā¦whatās being done to prevent these frequent events going forward? Give us an honest sign that efforts are being made to strengthen the foundation and maybe we can stop worrying about it a little.
Tried to phrase it as nicely and as nonconfrontationally (is that even a word?) as I could.
Itās a legitimate concern. Businesses are banking their livelihoods on having operational ERP 24/7. If theyāre down they canāt take orders, canāt ship, canāt bill, canāt forecast, canāt run MRP, canāt this that and the other thing.
No malice intended.
We just got out of a meeting on this very topic. Calculating how much we lost today because our ecom site was down, we couldnāt ship, etc.
Weāve had the same conversations here from time to time. When your partners start charging you back because you didnāt ship an ecomm order on the day it was promised, thatās an extra cost that youāre incurring due to not having a functional system.
We been talking about this for 4+ years (regarding Kinetic)- many more if you include all versions, but Iād love to see a breakdown of internal bugs/tickets charted across versions from Epicorās ticketing software.
Bugs for dinner anyone? - Kinetic ERP - Epicor User Help Forum
I ate those bugs for dinner man, or foot in mouth, or whatever we want to say there. Glad you pulled up the receipts.
No receipt intendedā¦just a flashback to a time nearly four years ago where many of the same issues persist. And weāre all dining on dragonflies these days.
Iām glad you pulled it up. @aosemwengie1 has respectfully told me Iām loony many times for continuing to say things like that, even at this last insights haha. I donāt blame her- I thought it would get a little better than this 4 years later.
4 Likes
We all hoped it would.
Let me go on record and say if it wasnāt 56 minutes into the day and I was a little more awake and caring, Iād think of some things that have gotten better- cause there are, but when it comes to stability and functionality of the system, I did think it would be more mature at this point. Weāre now having to re-think how to do BPMs and Data directives with EF coreā¦ Dealing with linux changeover, dealing with SSRS reports just randomly changing to an older version, application studio was wild for a while (I think it has improved?), you got pub sub breaking still (from what I glossed over) though it seemed like dashboards stabilized for a moment there.
The good things maybe- the cloud management portal has matured well. Idk maybe yāall can add to this. Iām not in Kinetic as much right now, the main company I work for is still 10.2.500, but we will be upgrading soon.