Bug: Duplicate DML Operation

[Mjohnson047]

It appears this rule is calling an error when there is assignment between two screens when there is a DML action between two screens with a previous button.

In this specific scenario we have an assignment setting a value to a variable and not an update to a record, so in this scenario it's not a DML action. Can you please review?

[junners]

Heya! Thanks for contributing to Lightning flow scanner. If you could share a sample flow, that would be great~

You absolutely got the rule correctly, if the DML is sandwiched between two screen elements and there is a "previous" on the trailing screen, chances are, when your user launches the screen flow and had gone past the DML element and previous was clicked, the original update would have been overwritten.