Job restarted 5 minutes after failed but without response action set up.

Eduardo Menezes (20 posts)
March 19, 2019 09:29 AM
Accepted Answer

I have one job that failed but after 5 minutes it started again automatically.

I can confirm that neither the job nor the step has response action to be restarted.

But I the failed and the next succeeded job have the same Chain ID.

As per image, you can see the job Instance 79 failed and restarted again Instance 80 with the execution reason automatically.

Does anybody know why this happens? Is it some configuration by default? Where can see it?

Thanks in advance.

Attachments

Bill Staff (599 posts)
March 19, 2019 09:43 AM
Accepted Answer

Responses can also be configured on Groups and Queues (and those inherited responses wouldn't be shown in the job diagram), so check the queue and group hierarchy that the job is in and see if the queue/groups have a Response configured.

Eduardo Menezes (20 posts)
March 19, 2019 09:52 AM
Accepted Answer

Perfect Bill.

I found it set as per attached image.

I do appreciate your attention and I glad you found the reason.

Best regards,

Replies are disabled for this topic.