Tips & Tricks

When debugging a Flow with modules that process messages at different speeds, disabling message queues can help trace issues more effectively. This allows each module to handle one message at a time, making it easier to follow the sequence of operations.

The 'Disable' and 'Show Selected' features are very useful when debugging complex flows, allowing you to limit testing scope by preventing certain modules from running and easily focusing on messages from specific modules in the Debug window.

In order to not lose any messages all modules in the Crosser library have built in retry capabilities. This feature is mainly useful on output modules that communicate with external systems.

The Window module is designed to create ‘windows’, or sequences of data points, from any number of sources. Check this article to learn how it works.

These modules can be used to send chat messages to Microsoft Teams. When sending chat messages you need to reference the destination chat by providing its ID. If you are using Microsoft Teams from your browser, you can find the chat ID in the URL when you open the relevant conversation.

The Split Module allows you to create condition groups to direct and route messages to various outputs.

To enable user authentication in the Control Center using an external directory server, you should configure one or more Identity providers through OpenID Connect.

Using Try/Except clauses is a good way of stabilizing custom code modules such as Python Bridge, IronPython, C Sharp or Java Script.

Use the HaltOnError setting to specify under which circumstances you want to stop or restart the flow.

As a general recommendation, you should always use the latest version of the modules in your flow. In this article we explain you how can easily update all modules in a flow with a single click.