Question
BPM Company
NL
Last activity: 27 Apr 2021 16:59 EDT
PegaMarketing 8.4.1 Campaign is not run properly
I'm trying to run a campaign in PM 8.4.1 but everytime i run i got an error in the strategy for each customer in the audience.
the error is only this: 2020-06-07 19:23:34,465 [ins], Partitions=[5]] [ STANDARD] [ ] [ ] ( mkt.offer.OfferBuilder) ERROR - validateProposition - Detected invalid strategy result with key: [/TesteIssue/TesteGroup/TesteAction]
There isn't any stacktrace or something else
I have success in one situation. Testing my campaign using a seed list
Based on this test I believe the error is related to something in the background and not with my artifacts
Have you had this error?
Thanks & Regards
-
Likes (1)
Durgarao Jeeri -
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
US
Per the referenced Support Case, the resolution was a local change: To overcome the issue, here are the two alternative options:
1. Create a Dataflow : Source as Customer RDBMS dataset => Destination as CustomerDDS Cassandra data set. Run it to load customer records to DDS. OR
2. Resave Context dictionary pointing Context Storage to Database table.
Pegasystems Inc.
IN
Have you added context shapes to your strategy?
BPM Company
NL
Yes. Customer context.
Pegasystems Inc.
US
Please raise a support case so they can investigate potential issues. You will need to supply them log files so they can investigate, so be prepared with that.
BPM Company
NL
Thanks @Saleem_A I raised a support case (INC-131132)
But if anyone from Pega community already faced this issue and would like to share the solution, feel free to reply
Pegasystems Inc.
US
@Raphael Jannuzzi Ribeiro, I suggested the support case because this looks pretty involved and is not something typical to be seen.
Accenture
AE
Dear Raphael,
Did you get any resolution for the error
ERROR - validateProposition - Detected invalid strategy result with key:
Coforge DPA UK Ltd.
IN
@Raphael Jannuzzi Ribeiro, Did you get the solution for this issue? I also have this issue
Accepted Solution
Pegasystems Inc.
US
Per the referenced Support Case, the resolution was a local change: To overcome the issue, here are the two alternative options:
1. Create a Dataflow : Source as Customer RDBMS dataset => Destination as CustomerDDS Cassandra data set. Run it to load customer records to DDS. OR
2. Resave Context dictionary pointing Context Storage to Database table.