Cube refresh utility and then essbase restart

we are doing some changes in our security and then we use the cube refresh utility to update the essbase applications.

After the utility is completed we are restarting the entire EPM environment.

this seems to more or less always cause one of our essbase applications to become corrupted?

Is this because EssBase will continue working with the refresh procedure even after the utility says it is done? If so how can I know when essbase is done and it is safe to restart it?

We have a lot more steps but this is the part we think is relevant. (we are starting with backup and exports then move on to ODI import of structures, some calculations and finally security import and refresh. Ending it all with a epm restart)