The Crosser module library has many modules to work with arrays, in this article we will go through the main use cases and the modules to use.

Credentials cannot be deleted if they are used in a read-only version of a deployed flow, as doing so would invalidate that version. If the flow version is no longer deployed/needed you can delete that version and then delete the credential.

Learn how to optimize your flows with metadata-driven stream processing, enabling efficient calculations, validations, and comparisons in in your data flows and pipelines.

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.

Examples of modules and solutions for making your data flow more resilient.

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.

Issue: You have installed the Node by following the instructions in the Node Installtion documentation but the Node does not show up as active in Crosser Cloud.

Follow these steps to troubleshoot these type of issues:

This article will provide you with some ideas how customers have implemented Crosser Node(s) in different infrastructures. Keep in mind that in all cases, the Node must be able to reach cloud.crosser.io via HTTPs port 443 in order to communicate.