It's a critical limitation for EF. The automatic recalculation of EF in case of OOO shoud act on EF modifying them where necessary, saving the existing ID

Very important this is fixed!

this seems like a pretty big miss . . . a nearly 4 year old idea with a relatively high vote count . . . and no update?!?!

As a user, I also would like to have this feature of PI Analysis. I am using a PI Connector to gather data with a specific past timestamp , and I need to trigger an EF based on those new coming data with old timestamps, but if the timestamp is too old, I cannot do trigger the EF based on the function HasValueChanged.

We found other ways to do it, but with an automatic recalculation, it would be easier.

Need this as well. This is a must have!

I would need this for EF as well - many EF's aren't being closed because of ooo events.

I need this for EFs, I have long running EFs that are not being closed due to OOO events.

We have a situation where lab data may be delayed in being passed into PI. Therefore, it's imperative that either simultaneous event frames need to happen (which is not a current option) or automatic backfill needs to occur. One of these options is a must have!

This could be an optional value a per event frame that could be configurable as a Boolean. If enable kick the automatic recalculation if any attribute change.

we have the same demand for this feature to get implemented! I voted for it:)

I think this is the same as;
https://feedback.osisoft.com/forums/555148-pi-server/suggestions/34695688-automatic-recalculation-of-event-frame-in-pi-analy

We have the same situation where events sometimes arrive out-of-order of tags that are input of an expression analysis with Recalculate analysis for out-of-order input events. As this output is used for an end trigger of an Event Frame, the event does not get closed sometimes. A manual recalc/backfill of the Event Frame analysis or a recapture of the created event frame manually fixes it.
So if the same option for recalculation for out-of-order(and for relative analysis) was available for Event Frame analysis, problem solved. ;)

Customer had Out-Of-Order values for inputs on an EF Analysis. This resulted in either No Event Frames being created, or Event Frames opened for a long time. Customer was backfilling the Analysis regularly but is very repetitive. This feature would definitely saving the customers some effort.

One of my big customers has many intermittent connections, so there is much out-of-order data, upon which they need to generate event frames for reporting.

is there a statement on this?

Create event frames that did not exist before the OOO events came in. Flag them as OOO to make clear why they did not trigger notifications at the time.

For event frames that would not have been created if the OOO events had come in at the time, rather than deleting them, flag them as ‘obsolete’ or ‘superseded’

As as PI Admin I want that a EF is automatically changed if for example the Trigger Tag is changing in the archived values from my PI system.
It could happen that we completly remove the start end trigger for a specific event in the archive. Correspontenly the EF should also removed automaticaly.
This is at least affecting the EF Generator