Jobs get timed out

rohit1231 · Post by **rohit1231** » Fri May 25, 2007 9:31 am

Hi guyz,
I encountered a strange issue with a Sequence. The sequence was supposed to trigger a job and then based on the success/failure of the job, a second job activity was to be triggerred. The strange part was that the first job never got triggerred but its status was reflected as finished OK in the sequence log on the basis of what the second job got triggerred.
I guess this may have some connection with timeouts or server not acknowledging the jobs in due time span....

I learnt sometime in the past that DS released some patch which can make the user change the timeout intervals...

Any help would be appreciated

chulett · Post by **chulett** » Fri May 25, 2007 9:50 am

Welcome Aboard. :D

First suggestion would be - no guessing allowed. Timeout problems throw -14 errors, did you get any of those? What makes you think the first job 'never got triggered'? The Sequence job should log a 'Summary run' message when it ends, have you carefully examined it?

ray.wurlod · Post by **ray.wurlod** » Fri May 25, 2007 2:08 pm

Look in the logs of the individual jobs and report back what you found there. In particular, did job 1 even attempt to start? What was its status?