RBF Schedule job didn't run
What would cause a scheduled job (build) to not start or run? We are running 7.1.1.3.0.0009. The help files states:
"When a scheduled job attempts to run, the system checks the job queue, the Run Limit property of the project and the Hard Run Limit system setting: * If instances of the project are already running, but the project Run Limit has not been reached, the job runs. * If instances of the project are already running and the project Run Limit has been reached, then the system setting Hard Run Limit is checked: o If Hard Run Limit is N (the default), the job is queued. o If Hard Run Limit is Y, then the job is not queued. This scheduled occurrence is skipped. Does this mean if the project Run Limit has been reached it doesn't run? We do not have the Hard Run Limit set to Y. We are planning our upgrade to 7.1.2, but does the application not log it somewhere when schedules do not start? Thanks, sljhhsc |
2 answers
What would cause a scheduled job (build) to not start or run? We are running 7.1.1.3.0.0009. The help files states: I don't recall that 7.1.1.3 logged that it didn't start schedules anywhere other than stdout of the bfsched process if some debug flags are enabled from support. In any case you're going the right direction with 7.1.2. There were multiple improvements in schedule handling, manifest refreshes and server tests that make those systems more reliable and consume less resources. I'd suggest 7.1.2.1 which was just released. |
|
Thank you for your response.
We will look to upgrade to 7.1.2.1. Thanks, sljhhsc What would cause a scheduled job (build) to not start or run? We are running 7.1.1.3.0.0009. The help files states: |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.