​@jpeters stumbled across this just now. We’re in the process of fighting this ourselves. Our change process is 3 layered, Peer, manager team, change team.  I have a workflow prior to the automation that uses the logical expression to check the assigned agent value against the peer approver and if so, reverts the change status and emails the agent (not ideal but business rules cannot do this as of right now).

You could do the same if you are looking for requester and change agent. Here’s what I have for change agent matching the peer approver field (dropdown we added) logic. Just swap placeholders around as needed:

{{change.agent.email}}=={{change.lf_peer_approver_email}}

If the agents are different, it will kick off approvals to the peer then the manager team. Initially, we put in a block that managers could not be change agents so I had to undo that and instead setup a condition where if the change agent is not a manager it continues as normal, otherwise I have a unique condition for each person on that manager approval board. When the match is found, it will send manager approvals to everyone except that manager (prevents self approving) and then the final change board.

Hopefully that makes sense if you never resolved this, and if anyone else stumbles on this they have an idea :)