Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Real time processing does not retrieve the latest record

SA-98249

Summary



User has configured two real time data flows.

The first real time data flow is configured to invoke the 'Capture response for previous decision in the past period' Strategy. In the Strategy, on performing a Data Join with an external input (Cassandra), the results do not display for the Join though the data matches. However, the same functionality works after restarting the data flow.
The second real time Data Flow is configured for the Capture Response flow. The Strategy shape in this real time data flow is configured to load the previous decisions from within the past 7 days. On starting this real time data flow, unable to Capture Response for decisions made after this time point.


Error Messages



Not Applicable


Steps to Reproduce

  1. Create two real time data flows.
  2. Configure a Strategy with the 'Capture Response for previous decision for the past period' mode in the first data flow.
  3. Send the Offer Response payload such that the real time data flow processes the incoming event.
  4. Configure the second data flow for the Capture Response flow.
  5. Configure a Strategy shape in the second real time data flow to load the previous decisions from within the past 7 days.
  6. Start this real time data flow. Unable to Capture Response for decisions made after this time point.


Root Cause



A defect in Pegasystems’ code or rules 

The Strategy shape on the realtime data flow is configured to load the previous decisions by time range (for example, for the last 7 days). The implementation behind this use case, must calculate the start and end times based on the system's current timestamp for every request. However, this start and end times are cached per data flow run inaccurtately. For a Real Time data flow, this is frozen to be the moment when the first request is processed by this data flow, and any decisions made after that time point are excluded by the time range criteria inaccurtately.


Resolution



This feature is implemented in Pega Platform 8.4.

Published April 2, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us