User receives journey task notification even though the AOR of the user has been end dated
Summary:
In our journey configuration, we have set of journey tasks that where performer is selected as Area of Responsibility say 'HR Specialist'.
We have a scenario where a journey was assigned to a person on 1st August 2025 and on that date the system identified the task performers to be all the representatives with the AOR 'HR Specialist'.
Now one of the representatives had an end date to the AOR assignment on 5th August 2025.
Expectation: That representative should not receive any notification for any journey tasks that was previously assigned to the AOR - 'HR Specialist'.
Current Behavior: The user continues to receive the notifications for the previously assigned journey tasks to be performed by the AOR - 'HR Specialist' even though the 'HR Specialist' AOR assignment is end-dated for the user.