You are viewing limited content. For full access, please sign in.

Question

Question

[Cloud] Business Process Activity Reached Maximum Iteration Loop of 50

asked on April 17, 2023

Hi all,

We have a business process in cloud which uses a workflow to check for a document in the repository every 24 hours.

If the document is not found within 50 days (i.e. the loop runs 50 times) the process becomes suspended with this error:

If I retry the task, I just get the same error again. Is there a way to move past this? Or is the only option to cancel the instance when this occurs?

I understand why the limit is there, just wondering how we can handle it on the rare occasion it occurs?

Cheers,
Dan

0 0

Answer

SELECTED ANSWER
replied on April 17, 2023

Why do a daily check instead of waiting in workflow for the invoice and having the business process wait for the workflow to complete?

0 0
replied on April 18, 2023

Hi Miruna,

That's a great suggestion thanks, should have thought of that! I'm just trying to implement it now though an am having some trouble. I've not used this activity in this way before so may just be that I'm doing something wrong! Would you mind taking a look please?

I have these steps, first find the folder the invoices are being saved into, then wait for that folder to change.

The condition is set to look at the contents of the folder and wait for any document which is created with the correct PO Number.

But when the condition gets evaluated it always comes back false?

The rule is being evaluated when I create a new document in the folder, but just returns false every time. Have I configured something wrong in the activity?

Thanks,
Dan

replied on April 18, 2023

Hi Miruna,

That's a great suggestion thanks, should have thought of that! I'm just trying to implement it now though an am having some trouble. I've not used this activity in this way before so may just be that I'm doing something wrong! Would you mind taking a look please?

I have these steps, first find the folder the invoices are being saved into, then wait for that folder to change.

 

The condition is set to look at the contents of the folder and wait for any document which is created with the correct PO Number.

But when the condition gets evaluated it always comes back false?

The rule is being evaluated when I create a new document in the folder, but just returns false every time. Have I configured something wrong in the activity?

Thanks,
Dan

0 0
replied on April 24, 2023

Testing this further it seems this is only an issue if the token being used in the "Wait for Entry Change" activity comes from an input parameter in the workflow. From my testing this seems to be an issue regardless of where the input parameter is coming from - I get the same problem if I pass the input parameter (in this case "PO_Number") from a form or if I just enter it when running the workflow from the designer.

Creating the token any other way (e.g. using the assign token values activity) seems to work fine. The work around I have put in place in this case is to save the input parameter into a new token using the assign token values activity, and then use this new token in the wait for entry change activity.

Could you please confirm if this is a bug?

Cheers,
Dan

0 0
replied on April 24, 2023

Yes, I can confirm the behavior for parameters and that it's not expected. Bug reference ID #423916.

1 0
replied on April 24, 2023

Thanks Miruna!

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.