Troubleshooting / Known Issues

📘

Troubleshooting error messages in logs?

If you are troubleshooting messages in application logs please check the Logs troubleshooting page

🔹 [FLOW] Problem with Switch to context option in Custom block

Problem: Using Switch to context option in a Custom block causes unexpected bot behavior:

  • returning from another context back to the Custom state causes overriding the currently chosen NLU model
  • returning from another context back to the Custom state causes that Response is used again by the bot

Solution: DON'T use Switch to context option in Custom block. Use a separate Context block for switching contexts.

🚧

Switch to context option in Custom block is deprecated and will be eventually removed in one of the future Automate releases as a final fix for this problem (this change will not break your previous projects)

🔹 [FLOW] Copy/paste feature in Flow module is not working

Problem: when the user copies and pastes the block in Flow module, nothing happens

Description: SentiOne Automate uses the browser Clipboard API. As the API is only available to Secure Contexts, it cannot be used from a content script running on http:-pages, only https:-pages. Check if HTTPS protocol is enabled.

🔹 [FLOW] Say with fallback use only first fallback response

Problem: when there is a second Start block in Flow (above the first one and without defined any output condition) - Say with fallback always return the first fallback response (fallback counter is not working).

966

Workaround: set any output condition in the second Start block