If this is intended behaviour, then I’m curious about if there’s a possibility of the Event Daemon firing off too fast for the calculated field to update.
I’ll explain with an example. On our Shot entities, we have Cut Duration that counts the number of frames in a Shot. We’ve also made a calculated field “Length”, which basically calculates the length of the shot in seconds, based on the Cut Duration.
Say we have a trigger that will post a note saying “Scene has been updated to Xs long.” that triggers when the Cut Duration is updated and uses the “length” of the shot. So the intended order of operations is:
Cut Duration Updates > Length Updates > Note posts
But is it possible that the calculation is delayed, leading to:
Cut Duration Updates > Note posts > Length Updates
which would mean the note posted with an incorrect length since it hadn’t yet updated.
I expect that this is at least unlikely because the event triggers running on our server should be slower than the calculated field. But is there a gap where this could theoretically possible? Particularly if there’s slowness on the databases end?