Sounds like either you have a scheduled event enabled or you have set the "turn off after time" APP set. My recommendation when trying to determine what is causing HG to do things is to first look at the activity log (has to be turned on in maintenance) and if that doesn't give enough detail check the log file. As a last step, you can output the mono output to a file or watch it interactively. When the module is turned off, one of these methods should give enough detail to determine what's doing it. Once you know what is driving the action, you can figure out a way to augment it to do what you actually want.