Lately some of my schedule jobs did NOT kick off for some reason, some day it works fine other day it doesn't. To work around this I would have to go into the schedule and clone the job and submit it as "Right Now" then come back and edit the scheduler by change the date or time then apply the changes so it can update the scheduler again.
Questions:
1. Is anyone encounter this error before and how do you resolve this?
- Is there a way to kick off the schedule job if not kick off by itself base on the date and time? Is there Soap API call that I can do to kick off the schedule job? I just wanted to kick off the schedule job since it already has the permission set in the scheduler already.
Please let me know.
Thanks,
Kham Sackpraseuth