My employer is a cloud customer on the latest version of Kinetic. For a few weeks now, Epicor Functions have been severely impacted by some kind of backend issue with Epicor where every single change (any update, or new functions, etc), requires a full App Pool Recycle in order to be able to use the new or updated function.
I’ll try to demonstrate the issue with an example-
Say you have a pre-existing functions library with a function in it that only returns a pre-defined string, lets say it just returns “test”.
You call the test function from postman, or any other way, and it returns the “test” string.
Now if you go and make any change to the function, let’s say change the string to “test change”, and save in functions maintenance, the updated function cannot be called until an app pool recycle has been performed by epiccare (very painful process).
That means if I call the updated function again, it still returns “test” instead of “test change”, because the updates do not “stick”.
Similarly, if I were to add a new library or function to an existing library, that new function/lib is not available for use until another app pool recycle has been performed.
So every change requires an app pool recycle to be performed in order to use the updated or new function. Suggestion from Epiccare is continued app pool recycles with each update or change.
The issue has brought any development involving functions to a grinding halt and it’s driving me crazy! I have a couple high priority projects with deadlines going on right now which hinge entirely on functions working and being able to test, develop, and deploy them in a reasonable amount of time.
It has been a ‘known issue’ for weeks. Has anyone figured anything out on the Epicor / Kinetic side that can be done to resolve this issue? It effects all 3 of our cloud environments the same. Including our Production / Live environment.
Any input or any hope on the horizon for this issue? I am willing to try anything at this point.
Thank you so much for reading.
