Issues with Optional Slots

Question

I am leveraging optional slots in a conversation process I have been building, but have 2 issues:

The conversation failed on setting a slot called conversation_context, that is set to Always Infer, with this error “hit an internal issue trying to build the conversation context and that specific run (execution <execution id>) has been stopped and cannot continue”. This has only happened once so far.
I have a user object slot that is getting populated via a notify statement. I have tried all 3 infer options and none of them have been successful in setting the user properly. I can no longer get this functionality to work that was working perfectly fine earlier today.

This last issue is big in that it seems to be is breaking notify statements sending a user object to a conversational process.

andrewwhitley · Answer

Scratch this - the issue was using null as the default value for object list slots. Once I ran the conversational process normally (not notify) I was able to see the error and then change the default value to empty object lists. I now need to find a way to get the slot to populate but that can be a separate inquiry.

Sign up

For current customers who manage their engagement with Moveworks, please login or create your account with the customer button below. For Moveworks Partners, please login or create your account with the partner button below.

Login to your Moveworks Community

For current customers who manage their engagement with Moveworks, please login or create your account with the customer button below. For Moveworks Partners, please login or create your account with the partner button below.

Scanning file for viruses.

This file cannot be downloaded