Null_resource with a destroy provisioner being destroyed for every trigger change

We have a null_resource provisioner with two local-exec (one with when = "destroy" ) and several triggers. Whenever one of the triggers changes (or shows known after apply) the null_resource is marked as must be replaced and seems to run the destroy provisioner and then the create provisioner, whereas I would expect that only the create provisioner would be run.

Is there a way to skip the destroy provisioner to run for every change of a null_resource?

Similar topics without an answer:

another similar topic to this question: