Question
JP Morgan Chase
US
Last activity: 16 Oct 2019 8:46 EDT
Work objects ending in flow error due to max flow count reached
In our application there are some work objects which has to go to recurring cycle and hence same set of flows are called every month and workobject is open since 2016.
Now in 2019 the work objects started going to flow error and the error says -
Could not embedded flow page, the limit of flows of the same type may have been reached. The limit pxmaxflowaddcount is 50."
My question is - when i go to clipboard of the workobject i don't see pxflow page group more than 10. What am i missing? Which property in clipboard should i go and check to see the flows has reached more than 50?
Pegasystems Inc.
US
What do you see for the flow names on the work object? When it goes through the same flow, you will see "flowname_count".
JP Morgan Chase
US
There is a property - pyFlowCalledCount and the value is 1 for all flows.. Is there any other property in clipboard i can check. I am trying to find out how many work objects can go through this flow error in next 2 months.
Pegasystems Inc.
US
What are you seeing for the flow name though under pxFlow pages? Do you see a counter at the end of the flow name?
Pegasystems Inc.
US
A flow can be repeatedly added to a work object by a loop calling the Flow-New activity method, or by a split-for-each shape.
There is a System Setting: pxMaxFlowAddCount, default is 50.
It is used by the AddFlow rule-utility-function.
Let's say the flow to be added is NewHire. If NewHire was already on the work object 10 times, the pxFlow subscripts would look as follows: NewHire, NewHire_1, NewHire_2, …, NewHire_10.
If AddFlow is called with a request to add NewHire yet again, it would loop over each of those NewHire entries, seeing that they are present, and trying the next index. In this case, NewHire_10 is available, so it would not stop at that. But if it got to NewHire_51, it would pull off the 51, realize it was greater than the (default) system setting value of 50, and return to its caller with an empty string.
A flow can be repeatedly added to a work object by a loop calling the Flow-New activity method, or by a split-for-each shape.
There is a System Setting: pxMaxFlowAddCount, default is 50.
It is used by the AddFlow rule-utility-function.
Let's say the flow to be added is NewHire. If NewHire was already on the work object 10 times, the pxFlow subscripts would look as follows: NewHire, NewHire_1, NewHire_2, …, NewHire_10.
If AddFlow is called with a request to add NewHire yet again, it would loop over each of those NewHire entries, seeing that they are present, and trying the next index. In this case, NewHire_10 is available, so it would not stop at that. But if it got to NewHire_51, it would pull off the 51, realize it was greater than the (default) system setting value of 50, and return to its caller with an empty string.
The ProblemFlow_AddFlowFail will display the below message: "Could not add embedded flow page; the limit of flows of the same type may have been reached. The limit pxMaxFlowAddCount is a Rule-Admin-System-Setting that defaults to 50."
JP Morgan Chase
US
I understand this part. If the workobject traverse same flow multiple times then we should see _2, _3 against the flow name in clipboard,
But i don't see a _50 or not even _40 on any flow name in clipboard. I can't share the entire clipboard since the clipboard has PI data but i am attaching the pxflow part of clipboard since that has no PI data and that is the part you might want to observer.
i am still waiting for a pega sme to set up a meeting as part of this issue ( i have raised an SR also) to show the entire clipboard and help me figure out why this error is really caused. ideally there is no count or no property that tells me this workobject traversed same flow 50 times.
Pegasystems Inc.
US
The clipboard for one page under pxflow will not have the information you need. You won't see any counter there.