Understanding message queues: Failed messages go to a dead letter queue and can be restored or deleted via the Node API if persistence is enabled.

Tracking dropped messages: With persistent messages enabled, dropped messages go to the dead letter queue and can be restored or deleted via the Node API.

All Crosser modules can keep messages until successfully delivered. To enable this feature you need to set the ‘Max Number of Retries’ setting to a value larger than the default 0.

If you have a flow with multiple paths, data could be processed differently depending on the message queue configuration.

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

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.

In this article we describe what options you have and how to utilize provided interfaces for integration into your monitoring solution.

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.

For unstable connections, store data locally and upload or stream it later to services like Azure IoT Hub or Kafka.

This module is commonly use to block messages with invalid data or to apply different processing based on message data.