When using user slots, 99% of the time they work fine. On occasion though they seem to return a list of the single user instead of a single user object even when the slot is not set to be a list. This causes the plugin to fail when trying to get a user attribute like their email address as it expects me to first get the user in the list. My workaround for this is to do the following expression to turn it into a list and then take the first entry:
requestorEmailAddress:
EVAL():
args:
normalized_req:
FLATTEN():
- data.requestor
expression: normalized_req[0].email_addr
However having to do this in every plugin and every place where a user object is being leveraged is a bit much.