quite weird. I have same trouble there.
But In my case task in progress says job is executing on HIGH priority however appserver/ or console log indicates that job is executed with NORMAL priority.
Same i checked the log, it was also executed at normal priority despite setting the PRIORITY * properties to "HIGH".
Anyone have any idea why? Or should i log a case?
Im on 8.3 sp3.
For Each role there is max allowed Job Priority. By default it is normal. Even if user tries to change it to High it will be capped at Max allowed to his role.
Login as RBACAdmins Role. Set "High" for MAXIMUM_ALLOWED_RUNTIME_JOB_PRIORITY* Property of that role using which you want to run the job. Then try running job using High priory.
yeah...now it is working as expected. Earlier it is executed with NORMAL only becoz of the capping set against the role with which the job is executed.
So follow Swapnil's approach and then update the PRIORITY property to HIGH for the job in question.
Works well thanks
didn't expect it to be capped for BLAdmin role