12-06-2016 07:52 AM - edited 03-01-2019 09:24 AM
I have a job that reruns every 5 minutes but if it completes abnormally the job stays in that status. In Tidal 5.3.1 this job would automatically reset itself and try rerunning in 5 minutes. I don't see anything different in the way the jobs are set up between the two environments. Does anyone know how to resolve this issue so that the job automatically resets.
12-06-2016 10:03 AM
Hello Frederick,
Are you stating that once the 1st failure happens, all other attempts automatically are noted as ' Completed Abnormally'?
snapshot your Schedule & Options tab so we can take a peak.
12-06-2016 10:16 AM
12-06-2016 03:05 PM
In your master database run the following (I show it in MSSQL):
select * from sysval where sysval_id = 93
If it is set to 'Y' then jobs will only rerun on 'completed normally'. If it is set to 'N' then the jobs should rerun even if it completed abnormally.
12-07-2016 11:13 AM
Hey Mike,
Is your SQL update the same as going to the System Configuration/ OTHER tab and putting a check box on 'Allow Job Rerun on any completed Normally and Completed Abnormally States"? just curious for my own information. thanks in advance.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide