wanted to get some thoughts on an issue we are facing for sometime. we’re on 25.1.2
this happend to our primary scheduler where the files is output as a CSV. some customer for reason will have two line of offers with everything the same expect for rank. some information i can think of to share
version: 25.1.2
constraint: select the top 1 OB context subscription
primary schedule is running on All issues/ All groups
in CDHDetailedInteractionHistory, the only difference is pyGUID, everything else is the same
To resolve duplicate outbound offers with identical rankings in Pega Customer Decision Hub 25.1.2, you should implement a Prioritization strategy component that utilizes a tie-breaking property to ensure a unique top selection. Since your constraint selects the top subscription but the records are identical, the system cannot naturally distinguish between them, leading to duplicate output in your CSV file. By adding a secondary sort criteria, such as @abs(pxCreateDateTime) or a specific SubjectID, you force the scheduler to pick a single, deterministic record. This adjustment effectively filters out the secondary lines in your primary schedule before they reach the file outbound stage. Once deployed, the interaction history will only record the single GUID selected by this refined prioritization logic.