Thank you for your quick response.
These 125 job scripttrigger do not happen at the same time. And each trigger takes within 1 minute. That means the probability of having many triggers at the same time is low. I checked all timestamp of log when trigger running normally. At most 3 job triggers happen at the same time. So that shall not be issue.
But when I checked the timestamp of log when scripttrigger did not work, the timestamp of more jobs are same (maybe more than 3 but I do not remember very clearly).
some of jobs use the same timer format
0 */3 * * *, 40 */2 * * *
Will that be problem?
Lastly, about your question to allan, slave is not off. In the jenkins web ui "scriptTrigger" only shows "polling is not run yet".And the scriptTrigger.log has no content although the timestamp shows it did recreate on time. So it does not looks like timer issue. It seems the log file is touched but can not proceed. Do not know where it is blocked.