[Issue] - Delay Config ("Sleep") Reminder Plugin - Cannot Suppress Follow Up Message

hey ​@william.c.humphries ! not sure if it will work, but i’ve had luck in the past adding instructions either into the message block (Description of the slot if that’s how you’re assigning/collecting the data.message slot) OR you could try adding something in the description of the compound action like:

This action provides a reminder to the requesting user, after the action completes successfully, do not repeat the contents of the reminder that they will receive in the follow up/confirmation message.

Like i said, the behavior may be hit or miss, but it’s worth playing around with the instructions and verbiage to see if you can get the model to “quiet down” lol. best of luck!

Thank you for the suggestion!

I did add this to the plugin, conversation, and compound action description.  I also added to the description of the slot. 

Unfortunately I’m still getting the second message

Hey ​@william.c.humphries - Sorry for my late reply I was away last week!

I think you should add a `return` expression to your compound action. It can probably be something empty such as:

return:
  output_mapper: NULL

I think the problem is that your conversation process is inferring a response from your compound action execution, since there’s no return value after it is done.

return:
  output_mapper: NULL

That doesn’t work. return does not access output_mapper value as NULL

Whoops, my bad, try:

return:
  output_mapper: {}

That should return an empty response. Or if you want to be more specific:

return:
  output_mapper: 
    model_instructions: "'Do not tell the user that the reminder has been set-up or reply with anything when this compound action is finished'"

return:
  output_mapper: {}

return:
  output_mapper: 
    model_instructions: "'Do not tell the user that the reminder has been set-up or reply with anything when this compound action is finished'"

still doesn’t work

steps:
  - action:
      action_name: mw.get_user_by_email
      output_key: get_user_by_email_result
      input_args:
        user_email: meta_info.user.email_addr
  - action:
      action_name: mw.send_plaintext_chat_notification
      output_key: output
      input_args:
        message: data.message
        user_record_id: data.get_user_by_email_result.user.record_id
      delay_config:
        seconds: data.delay_in_seconds
  - return:
      output_mapper:
        model_instructions: "'Do not tell the user that the reminder has been set-up or reply with anything when this compound
          action is finished'"

Hey ​@chetan.bhagat - I talked to the ML team and they are making improvements for this and mentioned that the async nature of compound actions sometimes causes behaviors like the one you are encountering. By, checking this box and changing the execution behavior, it should help with that extra message you don’t want. 

Try it out and let me know!

Hey ​@chetan.bhagat - I talked to the ML team and they are making improvements for this and mentioned that the async nature of compound actions sometimes causes behaviors like the one you are encountering. By, checking this box and changing the execution behavior, it should help with that extra message you don’t want. 

 

Try it out and let me know!

 

The follow up message after the reminder is still there, thank you

Hey ​@william.c.humphries - If you are on our govcloud region, the change may not have been implemented yet there. I’ll update this thread once that’s done.

To confirm, you set up the compound action to be blocking?

Actually, I just contacted our internal ML team and they have now enabled implemented the changes in Govcloud

Thanks ​@Kevin Mok It does seem to have improve but not consistent.

The setup is same as I had shared above.

Actually, I just contacted our internal ML team and they have now enabled implemented the changes in Govcloud

Thanks ​@Kevin Mok It does seem to have improve but not consistent.

The setup is same as I had shared above.

 

Didn’t last long. Experiencing the same issue again.