Skip to main content
5. Not Enough Info to Make Decision

Handle non-list user slots reliably

Related products:Agent Studio
  • June 29, 2026
  • 2 replies
  • 42 views

Forum|alt.badge.img+3

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.

2 replies

Kevin Mok
Forum|alt.badge.img+2
  • Community Manager
  • July 10, 2026

Hey ​@andrewwhitley this seems more like a bug rather than a feature request. I’d open a support ticket so our eng team can take a look at it. If you could share your conversation IDs to the support team that would be very helpful


Kevin Mok
Forum|alt.badge.img+2
  • Community Manager
  • July 10, 2026
Updated idea status1. New5. Not Enough Info to Make Decision