do Reload task failed but Automation status is Finished

[lessing]

Hello,

I built an automation with a "do reload", run mode "Wait for relaod to complete" and in settings on Error: " Stop - Stop Automation and set to failed". As you can see in the attached screenshot (QLIK_AUTOMATION_FAILURE) the status of reload  is FAILED but the automatic status is Finished (no indication of an error).  Is this the expected behaviour or is it a product error? I am expecting a status FAILED for the automation.

Regards,

Jürgen

[Shai_E · Accepted solution]

Hi Jürgen,

You may have set the blocks on error behavior to stop the automation and set it to failed state.

But the block never failed in returning back a 200 http response, the block simply returns the reload app log with the status of the reload and this is why the automation kept running.

If the Do Reload block would have failed with returning a response, any other failed http status the automation would have stopped as per the blocks On Error setting.

The Do Reload block queues the app for a reload and simply returns an object that includes that reload log and the status of the reload.

Best Regards

[lessing]

Hello,

that's what I feared. I have a chain of almost 100 reload jobs. This chain is already confusing. If I have to check the status after every execution of a reload job with a condition, then this is no longer manageable and I don't see the loading status of a reload in an overview. Is error handling implemented in the future workflow manager?

Best Regards

[Shai_E]

Hi @lessing ,

So the use case is if even one app reload fails out of the 100, stop the automation and set an error?

[lessing]

Hi,

yes, for example or as an option to set a warning and go on. In the moment everything is green and I don't get a hint that there is something going wrong.

[Shai_E]

Hi @lessing ,

Well, you could do something along the lines of looping through the apps, and for each app realod it, wait for the reload to complete.

check if the status of the reload is a success then do something

else you can use the error block to stop the task on the first instance of an app reload fail.

[lessing]

Yes, this is my workaround. I am using so many workarounds to run relaod tasks parallel, sync them and so on. Then I have to implement it in this way. It is a workaround no acceptable solution. Hopefully we will get an enhanced tool in future. 

Thank you for your reply.