This content has been marked as final. Show 2 replies
This is documented behaviour. It looks like you have "RESTARTABLE" set for the job. This flag always causes the job to retry after 1 second, 10 seconds etc up to 6 retries. The number or pattern of retries is not configurable.
Only when all of the 6 retries have failed or when the next retry would be after the next scheduled job run will the job be marked as failed and the failure count and run_count will be updated.
The max_failures attribute specifies after what number of failures the job will be disabled and marked as broken.
It sounds like what you are looking for is a max_retries attribute which does not exist since it is not currently supported.
If you do want to limit the number of retries, you will have to add application-level code to do this. One way to do this is to set restartable to false and add retry logic to your code.
See here for a description of "restartable" and of "max_failures"
Hope this helps,
Thanks for that. Yes it helps... I found the documentation though up until know a bit misleading I guess. Coming from dbms_job, the scheduler offers a lot more, and when I saw the max_failures attribute, figured it would allow us to control when the job stops executing. I did read over the documentation a few times, but for some reason, missed the details on the restartable attribute and retry intervals. I was also curious about how that was configured.