Hello !
I have a custom timer job in multi-servers environment, which is only executed when activated, through a powershell script.
My main problem is that, when the powershell runs the command "$job.RunNow()", the job is placed in the queue and sometimes the execution doesn't occur until the next day... And as I look in my script for a recent entry in the job history to get its status, it loops until the end of the execution of the job, sometimes the next day.
So my question is : is there a way to tell the owstimer to set this job to the top of the execution order ? I mean like "ok, this one is hot, you have to take it ASAP".
I though another solution : replace the "RunNow()" command by the "Execute()" one. But the problem is that there's no way apparantly to get the status of the execution, because this command avoids the owstimer...
Thanks in advance for your help !