So I think we’ve run it enough times now that I’ve generated an error due to logout occurring mid-trigger. In this case, the pairs of green and purple numbers should match after the app runs to completion, but there was an automatic timeout/logout event whcih appears to have caused a discrepancy.
After inspecting the table data for the two tables involved, it appears that the trigger actions for the table records for the top row of analytic numbers all executed completely, but when the interruption occurred, it happened just after the record ID for the second table (bottom row of analytic numbers) but before any of the other information was transcribed.
Also, the interruption could have occurred after any one of the trigger actions in the sequence, so there could be different degrees of missing data in the first or second table, and the second table record could be missing entirely.
I probably need to create a “repair” app to find and fix such records, but I was wondering if it would be technically possible in a future release of Tulip player to delay the logout until the current trigger has completed.
In Office Hours discussions this week, we contrasted the “danger” of altering the player behavior to wait for a trigger to complete before logout, versus the alternative of having an exception process for the automatic timeout/logout based on station or app or user (e.g. superuser). I think the latter option would largely resolve this issue (excepting any other type of interruption of the player session).
(related topic: Station indivdual timeout options)
We also discussed the fact that this app could be replaced by Automations, which is the logical evolution of this process once we upgrade to an LTS that has that feature.