A custom Event Action configured with a Stream Message action type works fine when sending a notification to a single user via the Receiver window, but adding a second user (which displays as a semicolon-and-space-delimited list, like 'User1; User2') causes the event to fail with 'The Foundation1 user "User1;User2" does not exist.'

All FAQ questions / Integrations and APIs

Answer

Replace the semicolon-and-space delimiter the Receiver window displays with a plain comma and no space (User1,User2) — the Stream Message action's underlying user-list parsing expects a comma-delimited format, not the semicolon-space format the Receiver window happens to show when you select multiple users from its list, and editing the delimiter to a comma resolves the 'user does not exist' error for multi-recipient Stream Messages.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions