Dynamic running sometimes doesn't update when UI inputs change about dynamo HOT 2 CLOSED

Other potential solution: setting IsDirty to true kills current execution and the re-evals.

Pros: potentially faster, less likely to get garbage data, can rollback the transaction so document will never get updated.
Cons: could result in unexpected run issues and element states which are unaccounted for. With DMU might not be a problem, but still potential unexpected thread issues may arise.

from dynamo.

IsInteractive attribute can now come into use. If true, eval is wrapped in dispatcher. Entire eval needs to be wrapped (from checking if cancelled to setting IsDirty to false) in order to avoid race conditions. Once the eval cancellation flag is set, IsDirty can NOT be set to false before the evaluation actually stops.

from dynamo.