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.

Incorrect order of events

Suggest edit Updated on September 10, 2021

During the processing of a data flow work item that contains an event strategy, the following error is displayed:

Event from the past. Current time in the Event Strategy: <YYYYMMDD'T'HHmmss.SSS> while the time in the inserted event was <YYYYMMDD'T'HHmmss.SSS>, as shown in the following example:

Event from the past error message

Event from the past error

Cause

This error occurs when the time stamp of the incoming event is older than the time stamp of the most currently inserted event. This error can be caused by one or more of the following conditions:
  • Events are inserted into the stream data set by a web socket or a POST method request from more than one thread, which can result in the wrong order of events.
  • The data flow that contains the event strategy is run in batch mode. In this case, events might not be sorted by date.
  • The data set that sources the data flow has formatting issues. For example, the data set might source data that is time zone-dependent, but the time zone code is not provided in the event records or the code is not correct.

Solution

Depending on the root cause of the error, perform one of the following actions:

  • Limit the number of threads that can send events simultaneously, or configure your application to send events from a single thread.
  • Use a report definition to sort events by time.
  • Review the data set that sources events to your event strategy for any formatting issues and correct them.
  • Previous topic General tips for troubleshooting adaptive models
  • Next topic Interaction History component processes data longer than expected
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us