>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3238631. --> Reported by: [mxh](https://www.drupal.org/user/1124384) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>This idea was mentioned by @jurgenhaas at a team meeting:<br> A user should be able to perform a dry-run on existing ECA instances, meaning that the dry-run would just go through all the conditions but would not apply the changes made within actions being executed. This might be thought as an approach similar to an <code>rsync</code> dry-run.</p> <p>Providing the ability to perform dry-runs will help on investigating possible problems within given ECA configs. It could also be used as a "try it out and see if it works" feature for end users.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>We may need to consider if we want to support both "dummy" content entities and/or real existing records.</p> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>