Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Incorrect order of events

Updated on July 5, 2022

During the processing of a data flow work item that contains an event strategy, the system displays an error stating that the time stamp of an incoming event is older than the time stamp of the most recent event.

You might see the following error message: 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

The following figure shows a sample error:

Event from the past error
A report showing errors for a data flow run shows one error.

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:

Cause: More than one thread is sending events

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.


  1. Limit the number of threads that can send events simultaneously, or configure your application to send events from a single thread.

Cause: Events sorted by date

The data flow that contains the event strategy is run in batch mode. In this case, events might not be sorted by date.


  1. Use a report definition to sort events by time.

Cause: Formatting issues in the data set

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.


  1. Review the data set that sources events to your event strategy for any formatting issues and correct them.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us