1 of 1 people found this helpful
Thanks for reaching out to us on PI Square.
If an analysis is event-triggered for two different attributes that have updates with the exact same timestamp, the analysis will only run once at the timestamp.
If an analysis is triggered and then shortly thereafter triggered again before the first completes, the second triggering of the analysis will be put in a queue to be processed when there are some free resources and the Analysis service will evaluate the analysis with the values of the attributes at the time of the triggering rather than the execution time. It's worth noting that if the Analysis Service is falling behind, that is to say analyses are triggering faster than the service can evaluate them, it will shed some of the load by skipping some executions to ensure that it doesn't fall too far behind.