Skip to main content
Question

AI Assistant claiming "Success"/"Approved" before user clicks the Notify action button "Approve Timecard"

  • February 9, 2026
  • 8 replies
  • 111 views

Hi everyone,

I am building a Plugin in Agent Studio that retrieves a user's timecard details and presents them with an "Approve" button using a Compound Action. I am running into an issue where the Reasoning Engine hallucinates a successful approval status immediately upon displaying the card, rather than waiting for the user to click the button.

The Goal
Plugin triggers (e.g., "I need to approve my timecard").
Compound Action fetches data, formats it using LLM, and sends a notify message with an "Approve Timecard" button.
The Bot should say: "Here are your details, please review and approve."
The Issue
When the plugin runs, the bot outputs the following message at the top of the response sometimes at the end, before the timecard details:

"Your timecard has been retrieved and successfully approved."

It seems the AI believes that simply running the plugin successfully means the business process (approval) is complete.

My Setup:

I am using a Compound Action called via an Action Activity in a Conversational Process. Here is the YAML logic:

Timecard_Approval_Flow

steps:
  - action:
      action_name: User_Lookup
      output_key: user
      input_args:
        user_email_address: meta_info.user.email_addr
  - action:
      action_name: adhoc_retrieve_timecard_employee
      output_key: timecard_details
      input_args:
        person_number: data.user[0].allExtension.accrualExtension.personNumber
  - action:
      action_name: mw.generate_text_action
      output_key: timecard_formatted_details
      input_args:
        system_prompt: "'You are a helpful HR assistant...'"
        user_input: # ... (Formatting logic here) ...
  - action:
      action_name: mw.get_user_by_email
      output_key: target_user
      input_args:
        user_email: meta_info.user.email_addr
  - notify:
      output_key: response
      recipient_id: data.target_user.user.record_id
      message: data.timecard_formatted_details.generated_output
      actions:
        - key: approve
          label: "'Approve Timecard'"
          system_action:
            action_name: adhoc_timecard_approval
            input_args:
              enddate: data.timecard_details.endDate.$SPLIT("T")[0]
              startdate: data.timecard_details.startDate.$SPLIT("T")[0]
  - return:
      output_mapper:
        status: "'Pending Review'"
        display_instruction_for_model: "'STOP. The task is NOT complete. Do NOT say the timecard is approved. The user must review the details below. Say exactly: Here are your timecard details for review.'"

Troubleshooting Steps Taken So Far :

Added Display Instructions: I added a return block at the end of the Compound Action with strong display_instruction_for_model telling the AI to stop and specifically NOT say "Success".
Checked Progress Updates: I verified the Action Activity in the Plugin Editor to ensure there are no "On Complete" messages configured that say "Success".
Plugin Output Mapping: I verified that the output of the Compound Action is being mapped back to the Conversational Process.
despite these instructions, the bot still defaults to a success message. How can I force it to remain neutral?

 

UX reference

Thanks!
@DIANA.TWC  ​@Kevin Mok  ​@ajohanson 

8 replies

Kevin Mok
Forum|alt.badge.img+2
  • Community Manager
  • February 9, 2026

Hey ​@RakeshTWC - Do you know if the compound action has the checkbox  “Wait for this action to fully complete before resuming the rest of this Conversational Process”? turned on?


  • Author
  • Participating Frequently
  • February 9, 2026

Hey ​@RakeshTWC - Do you know if the compound action has the checkbox  “Wait for this action to fully complete before resuming the rest of this Conversational Process”? turned on?

Yeah, It’s turned on.


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

@RakeshTWC Since your conversation process doesn’t depend on that compound action. Have you tried disabling that checkbox to see if the current behavior presents itself?


  • Author
  • Participating Frequently
  • February 12, 2026

 ​@Kevin Mok  Hi, Yeah. that auto approved message is changed to a different message. Please check the attached Images. I want to remove the end message so that it will be a good experience.


 

 


DIANA.TWC
Forum|alt.badge.img+6
  • Inspiring
  • February 18, 2026

Hi ​@ajohanson - This is a new issue we are tracking. It is very concerning behavior shown by Wond-E when no other changes were done in the use case. What else can be done to get support and get this resolved as soon as possible?


Kevin Mok
Forum|alt.badge.img+2
  • Community Manager
  • February 18, 2026

Hi team,

 

That last message happens due to the nature of the product; we always return a response. It’s currently something that’s not configurable and cannot be removed. For now, I see that it’s not providing that “your timecard has been approved” message, so that’s a good step forward.


DIANA.TWC
Forum|alt.badge.img+6
  • Inspiring
  • February 18, 2026

Hi ​@Kevin Mok - this was not the behavior of the agent before, these ‘summary’ messages were not showing up in this manner, and we want to remove them because they can cause confusion with the user.

The summary at the end is not ideal but manageable, however the language Wond-E is using at the beginning of the flow can be interpreted the wrong way. I just triggered this use case again and I’m still getting a weird set of commentary by Wond-E. (see below)

 

Can this be limited with more prompt guidance, or what action can we take? If anything, this summary space should be used to guide the user on what to do next.

 


Kevin Mok
Forum|alt.badge.img+2
  • Community Manager
  • February 18, 2026

Got it, if this wasn’t happening before it may be due to the change of going from GPT 5.1 to 5.2.

 

However, we may be able to change this. There’s 2 ways that you could steer the behavior.

  1. Add a more detailed description on the Conversation Process as to WHAT you want the users to see
  2. Do the same as above, but instead add a Content Activity before the Compound Action runs to try to steer the initial message.

Let me know if those approaches work for you, if not we can brainstorm some other ways to steer the message.