We are talking about a relogger profile that is running and has many tasks and was running before the problems appeared. If at some point changewowpath of pofile changes (in my case, the disk volume with wow folder simply disappeared due to a malfunction), the profile will not stop and will not throw an exception, but will continue to execute tasks, but instead of running the changewowpath task, before each Run Task, it will run wow.exe from the general relogger settings.
I think that the relogger should throw an exception if the wow path from the ChangeWowPath task is not found, even if there were no problems when starting the profile. That is, the check for the existence of the path should be not only at startup, but also inside the profile task loop.
-
changewowpath error
User Feedback
Recommended Comments
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now