Hi Pega Team,
Not sure what is the purpose of “Rule-Decision-Stream” feature introduced in V87. When I was trying to open and understand the purpose, I see an attached err in the PE. Pls check and correct it.
Hi Pega Team,
Not sure what is the purpose of “Rule-Decision-Stream” feature introduced in V87. When I was trying to open and understand the purpose, I see an attached err in the PE. Pls check and correct it.
@Ravi Kumar Pisupati I was also not able to find any documentation about that "Rule-Decision-Stream" rule, nor other examples of users encountering that particular error.
We will check internally, but could we first check with you whether you see any errors in your logs?
Is this a new installation?
Could you check the status of the nodes as suggested in the following post?
Can you provide details of what you see when you go to the following?
Dev Studio - > configure ->Decisioning → infrastructure → Services → Stream.
@MarijeSchillern - Pls check my answers to the asked qns.
Is this a new installation? This is my personal edition running on localhost:9090
Could you check the status of the nodes as suggested in the following post? https://collaborate.pega.com/question/error-stream-service-not-running-cluster
Yes I did check and I am good on this as well. Attached screenshot
Can you provide details of what you see when you go to the following? Dev Studio - > configure ->Decisioning → infrastructure → Services → Stream. => Attached screenshot.
I believe that this is a product bug and that is why I posted in Ideas forum.
Thanks,
Ravi Kumar.
@Ravi Kumar Pisupati in order for our support team to investigate, replicate and log the product bug please could I ask you to log the issue in My Support Portal so that we can have the engineering team log and fix the problem?
@Ravi Kumar Pisupati as per the analysis done on the linked support ticket, we have received confirmed from the engineering SME on the reported new rule “Rule-Decision-Stream”.
The Rule “Rule-Decision-Stream” was added by mistake under "Decision .
It is safe to ignore it and as confirmed it will does not have any functional impact.
We have raised a Cosmetic BUG-708697 and it will be taken care of in 8.7.1.
@MarijeSchillern - Thank you for the response.
Thanks @Ravi Kumar Pisupati!
I have updated this post and linked this to the Incident in Pega Support.