Issue Summary

In some of the Automation when the scope has been changed the previous projects might not be removed from the end. This results in Automation to execute the triggers with the old scope.

Steps to Reproduce

1. Create an Automation with multiple projects in the scope.
2. Remove one of the projects from the scope.
3. Trigger the event from project which was removed from the scope.

Expected Results

Automation should not trigger for the events from projects which was in scope before the change.

Actual Results

The automation is triggering for events from projects not in scope.

Workaround

1. Disable the Original automation rule.
2. Create a copy of the original rule and enable that copied rule in the required project scope.
3. Then trigger the rule as you did for your previous test in the project which is in question and the issue seems resolved.