Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Blue Prism AD01 Exam - Topic 1 Question 81 Discussion

Actual exam question for Blue Prism's AD01 exam
Question #: 81
Topic #: 1
[All AD01 Questions]

Please refer to the exhibits.

A Developer has created the logic that is resulting in an infinite loop of exceptions when the Multi Calc stage is executed

What is the reason"?

Show Suggested Answer Hide Answer
Suggested Answer: A

Exception Handling Logic:

When using ExceptionType() and ExceptionDetail() functions, they must be used within the context of an active recovery stage. These functions retrieve details about the current exception.

Issue in Logic:

In the provided diagram, the Capture Exception Detail stage is executed as a multiple calculation stage but is not within a recovery block. Using these exception functions outside recovery mode can cause another exception.

Resulting Infinite Loop:

This causes a new exception each time the Capture Exception Detail stage is executed, leading to an infinite loop of exceptions as the process continuously tries to recover from the newly generated exceptions.


Blue Prism documentation on proper use of exception functions and recovery stages.

Contribute your Thoughts:

0/2000 characters
Sherill
4 months ago
I'm surprised this wasn't caught earlier in testing!
upvoted 0 times
...
Romana
4 months ago
B sounds plausible too, but I'm leaning towards C.
upvoted 0 times
...
Denny
4 months ago
Wait, could it actually be D? Same names causing issues?
upvoted 0 times
...
Jacqueline
4 months ago
Definitely agree with C, that makes the most sense.
upvoted 0 times
...
Laine
5 months ago
I think it's option C, no Exception stage used.
upvoted 0 times
...
Lashandra
5 months ago
I’m a bit confused, but I think the Data Item names being the same as the Exception expression could cause issues. That seems like a possible reason too.
upvoted 0 times
...
Lyda
5 months ago
I feel like I’ve seen a question like this before. Maybe it’s about not using an Exception stage to report Exceptions, which could lead to an infinite loop?
upvoted 0 times
...
Cherry
5 months ago
I'm not entirely sure, but I remember something about blocks in the Recovery stage. Could it be that a Block isn't used, causing it to catch all exceptions?
upvoted 0 times
...
Shantay
5 months ago
I think the issue might be related to the Exception functions being used outside of recovery mode. That sounds familiar from our practice sessions.
upvoted 0 times
...
Dong
5 months ago
This is a tough one. I'm a bit confused by the different options, but I'll try to break down each one and see which one best fits the description of the issue.
upvoted 0 times
...
Mi
5 months ago
The key here seems to be understanding how the exception handling is set up. I'll need to pay close attention to the use of exception functions, recovery mode, and exception stages to identify the root cause.
upvoted 0 times
...
Irma
5 months ago
Okay, the question is asking about the reason for an infinite loop of exceptions in the Multi Calc stage. I think I'll start by looking at the exception handling logic to see if there are any issues there.
upvoted 0 times
...
Yuette
5 months ago
Hmm, this looks tricky. I'll need to carefully review the exhibits and question to understand the issue before selecting an answer.
upvoted 0 times
...
Chun
5 months ago
I've got a strategy for this - I'll carefully read through the question and exhibits, then systematically evaluate each answer choice to determine the most likely reason for the infinite loop.
upvoted 0 times
...
Myra
6 months ago
I think the key is finding a balance between meeting the supplier's needs and getting the best deal for our company. Shortening the payment period but asking for a discount could be a good compromise.
upvoted 0 times
...
Serita
1 year ago
Haha, I bet the developer wishes they had a 'MultiCalc Infinite Loop Remover' tool. That would make this a lot easier to solve.
upvoted 0 times
...
Truman
1 year ago
D seems plausible. If the Data Item names are the same as the Exception expression, that could definitely cause issues. Gotta watch out for those naming conflicts!
upvoted 0 times
Joseph
1 year ago
Definitely, paying attention to details like that can save a lot of time and headaches in the long run.
upvoted 0 times
...
Latanya
1 year ago
Yeah, it's important to be careful with naming conventions to avoid those kinds of issues.
upvoted 0 times
...
Dante
1 year ago
I agree, naming conflicts can really mess things up.
upvoted 0 times
...
...
Iluminada
1 year ago
That's a valid point, but I still think it could be because an Exception stage is not used to report Exceptions causing the infinite loop in the recovery logic.
upvoted 0 times
...
Micaela
1 year ago
Hmm, I'm not sure. The infinite loop of exceptions sounds tricky. I'll have to think this through carefully.
upvoted 0 times
Victor
1 year ago
Make sure the Data Item names are not the same as the Exception expression to avoid their own exception.
upvoted 0 times
...
Myra
1 year ago
It could also be that an Exception stage is not being used to report Exceptions, leading to the infinite loop.
upvoted 0 times
...
Olen
1 year ago
Maybe the Block is not being used for the Recovery stage, causing it to catch Exceptions from all stages.
upvoted 0 times
...
Barabara
1 year ago
I think the issue might be with the Exception functions being used outside the recovery mode.
upvoted 0 times
...
...
Ligia
1 year ago
I think the answer is B. A Block is not used for the Recovery stage, so it's catching exceptions from all stages on the page, causing an infinite loop.
upvoted 0 times
Natalya
1 year ago
Yes, using blocks for recovery stages can help prevent those infinite loops of exceptions. It's a good practice to follow.
upvoted 0 times
...
Howard
1 year ago
I agree, that makes sense. It's important to use blocks for specific stages to avoid catching exceptions from all over.
upvoted 0 times
...
Vivan
1 year ago
I think the answer is B. A Block is not used for the Recovery stage, so it's catching exceptions from all stages on the page, causing an infinite loop.
upvoted 0 times
...
...
Katina
2 years ago
I disagree, I believe it's because a Block is not used for the Recovery stage causing it to catch Exceptions from all stages on the page.
upvoted 0 times
...
Iluminada
2 years ago
I think the reason for the infinite loop of exceptions is because the Exception functions are used outside the recovery mode.
upvoted 0 times
...

Save Cancel