Skip to main content

We have noticed when building assistants there are some scenarios where pressing ‘enter’ will trigger the finish command and other functionally identical scenarios we have to press ‘enter’ twice to trigger the finish command. In the twice key press scenario, simply opening the debug console will allow this scenario to execute as intended.

 

I want to know if there is any way to identify why this is happening. The interplay between a validate command completion and when the finish command is executed is where we have noticed this inconsistency.

 

Any help or shared experience would be very much appreciated.


​@IFS Community ​@IFS Elite Solution Experts

This behavior is likely related to the sequence between client validation and the finish command execution in IFS Cloud Assistants. Client validations can be asynchronous, and in certain cases the first Enter key press may only trigger the validation, while the actual finish action requires a subsequent key press once validation has completed. Opening the debug console may affect timing, which is why the scenario appears to work as expected in that state.

To address this, I would recommend reviewing the assistant design to ensure that the finish command is executed only after the validate command has fully completed. If the issue persists, capturing logs using the IFS Cloud Web Debug Console (Client Logs and Network traces) and raising a support case with IFS will help identify whether this is a product issue.

Terms & ConditionsCookie settingsAccessibility statement