Error Handling not Stopping Task

[TylerMitton]

I've attached a task that shows this issue.

In my task I have a loop and in that loop there is something that causes an error (in this case I'm using a bad DB connection string cause an error). Around the loop I am using error handling that is set to stop the task when an error is encountered.

If the db connection is the only thing inside the loop then the error handling stops the task the first time it goes through the loop... as expected. The task is then done.

But if I put anything else inside the loop, even a comment, it will cause the error handling to not stop the task when the error is encountered... it will keep looping through until the loop condition is satisfied (in my case I set it to loop 10,000 times).

Why doesn't it stop the task as it is supposed to?

I want to put error handling around my entire task but this behavior means that it doesn't work as it should...

[forumsupport]

Hello,

We could reproduce the issue at our end. To get around this what you can do is, move the Error handling block inside the loop. We have attached the amended task for reference.

Hope that helps.

[TylerMitton]

Hi, I have several loops and sub loops (and sub sub loops) in my tasks, so I can't put error handling inside each of my loops... I would end up with a mess of error handling blocks that would be nightmare to work with. I want to contain my entire task inside a single error handling block.

Do you acknowledge that this is a bug? Will you be trying to fix it?

When it continues to loop through after an error has occurred, does it actually perform any of the operations in the task or is it just looping through and not doing anything?

It seems to me that it isn't actually doing anything other than looping without performing any actions. If this is the case, it is not a big deal if you don't have too many loops... but in my case I have 10,000 loops so it wont stop until it goes through all 10,000 loops... which may take a minute or so. That's too long to wait.

Thanks for looking in to this, I look forward to a fix being implemented!

Tyler

[forumsupport]

Hello,

You can use multiple Error Handling Commands in a single task inside each loop.

We have forwarded this issue to the product development team for fixing it in the future version of product.

[TylerMitton]

One thing you didn't answer... and this is important for anyone using error handling:

When it continues to loop through after an error has occurred, does it actually perform any of the operations in the task or is it just looping through and not doing anything?

[forumsupport]

Hello,

If an error occurs in the task and you have set the task to continue on error then task would continue after the Error Handling block. Task would stop executing commands after Error Handling block (i.e. End Error Handling command) in case you have set the task to stop on error.

Hope that helps.

[TylerMitton]

But even if you have told it to stop on error, it keeps looping through loops that are withing the error handling (as we discovered above)... it does not stop until it has gone through the loops. so...

Can you confirm that while it is looping through these loops it is NOT performing any other actions?

[forumsupport]

Hello,

Yes, if error occurs inside the loop then while looping, the task will not execute the commands after the line that errors out.

Hope that helps.

[TylerMitton]

With respect to this issue... back in January you said: "We have forwarded this issue to the product development team for fixing it in the future version of product."

Now that "the future version of product" has been released, can you confirm that this was included in version 6.0?

You really need to create a KNOWN RESTRICTIONS sticky thread so we can all keep track of these bugs in the software so everyone is aware of what is going on and what isn't working properly.

[forumsupport]

Hello,

Yes, it is fixed in Automation Anywhere 6.0.