Getting below error when trying to use a new adaptive model.
Trying to score invalid model!. Model key has empty context values: {"configPartition":{"partition":{"pyClassName":"SXM-Data-Customer-NBA","pyPurpose":"OfferAdaptiveModel_GAPA_Upgrade"}},"modelPartition":{"partition":{"pyChannel":"ContextNotDefinedError","pyDirection":"ContextNotDefinedError","pyGroup":"ContextNotDefinedError","pyIssue":"ContextNotDefinedError","pyName":"ContextNotDefinedError"}}}
This error is occurring only when we use the new model. When we substitute the old model from which the new model was copied, it works fine. Everything else is the same. Please let us know what is the issue.
Thanks.
Accepted Solution
Updated: 19 Feb 2021 15:59 EST
FutureproofAI
US
Thanks everyone. I had the adaptive model in 3 paths in a strategy and it was giving this error. I added an additional model component before the 3 paths and that seems to fix the problem even though all 3 paths had all the contexts set which was thoroughly tested.
Pegasystems Inc.
FR
This might be a valid error message. Can you share some configuration details.
FutureproofAI
US
FutureproofAI
US
Updated: 16 Feb 2021 18:08 EST
FutureproofAI
US
@MarcLasserre_GCS above I have attached the images of the context and settings. for the predictors, the customer attributes were all populated.
This is exactly as another model rule from which this model rule was copied over. That is working if we swap out for this in the strategy.
Please let me know if you need any other info. Thanks.
FutureProof AI
GB
@HansaS920 Hi, can you share the strategy that you are using this adaptive model? If any record passes ADM without any context empty this is the error it gives.
Thanks,
Anil
DCS
GB
@recepanilaydemir , Please check the Strategy logic & ADM component inputs. Looks like context param passed as null/empty resulted ContextNotDefinedError.
Thanks,
Nanjundan Chinnasamy | PEGA Lead Decisioning Architect
Accepted Solution
Updated: 19 Feb 2021 15:59 EST
FutureproofAI
US
Thanks everyone. I had the adaptive model in 3 paths in a strategy and it was giving this error. I added an additional model component before the 3 paths and that seems to fix the problem even though all 3 paths had all the contexts set which was thoroughly tested.