Not sure if this is a bug or just how DAT executes work, but my example below seems logical to me, but it seems like the python script happens so fast, the DAT execute doesn’t pick up the change in the table?
toofast.1.toe (4.06 KB)
Even more extreme examples show the same results.
toofast.3.toe (4.09 KB)
it is not a bug. the DAT execute is only comparing the before and after table once per frame. your changes all occur within a script in a single frame, but the tables at the start and end are the same, so no changes are detected.