Sometime back we come across an issue in ibot. the ibot was running only once.
on analysing, we found that the next schedule time is getting update with randon date.
on further digging we found that, one more scheduler in different time zone was accessing this nq_job table.
Upon fixing it, ibot started running without any issue.