You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when errors occur within a block execution ❌ (for example, due to expired credentials or API failures), there isn't a clear or user-friendly way to handle them.
I recently encountered an issue where my chatbot stopped sending emails because the credentials had expired. In such situations, it would be highly beneficial to be able to display a message to users informing them of the problem and guiding them on how to proceed, for example: "Oops, a problem has occurred, please contact us through another channel."
This feature proposes adding an "Error and Exception Handling Block" (or similar) to the block execution flow. This block would allow users to define specific actions to take when a preceding block fails to execute correctly. This could include:
Displaying a custom error message to the user.
Logging the error for debugging purposes.
Redirecting the flow to an alternative set of instructions or a fallback block.
Triggering notifications or alerts for administrators.
By implementing this feature, we can significantly improve the robustness 🛡️ and user experience of our chatbot ⚡ (or any block-based system) by gracefully handling errors and providing informative feedback to users when things go wrong. This will empower users to manage error scenarios effectively and ensure a smoother overall workflow.
The text was updated successfully, but these errors were encountered:
pierrejo
changed the title
[FEAT] - Add Error and Exception Handling Block for Block Execution
[FEAT] - Add Error and Exception Handling Block
Feb 5, 2025
Currently, when errors occur within a block execution ❌ (for example, due to expired credentials or API failures), there isn't a clear or user-friendly way to handle them.
I recently encountered an issue where my chatbot stopped sending emails because the credentials had expired. In such situations, it would be highly beneficial to be able to display a message to users informing them of the problem and guiding them on how to proceed, for example: "Oops, a problem has occurred, please contact us through another channel."
This feature proposes adding an "Error and Exception Handling Block" (or similar) to the block execution flow. This block would allow users to define specific actions to take when a preceding block fails to execute correctly. This could include:
By implementing this feature, we can significantly improve the robustness 🛡️ and user experience of our chatbot ⚡ (or any block-based system) by gracefully handling errors and providing informative feedback to users when things go wrong. This will empower users to manage error scenarios effectively and ensure a smoother overall workflow.
The text was updated successfully, but these errors were encountered: