Micro-Integration Flows now support configurable error handling to prevent data loss when messages fail during processing or delivery. Two independent features are available:

• Retry automatically re-attempts failed publishes using exponential backoff.
• Flow Dead Message Queue (DMQ) captures messages that can't be processed or delivered so you can inspect, reprocess, or discard them without losing data.

Both are disabled by default and can be enabled in any combination per Flow.

The error handling logic distinguishes between two failure types:

• Processing errors—such as validation failures or type mismatches—are considered unrecoverable and route directly to the DMQ without retrying, because retrying the same malformed message would always fail.
• Publishing errors—such as network issues or a temporarily unavailable target—are treated as potentially transient, so retry triggers first, with the DMQ as a fallback after retries are exhausted.

This feature is designed for sources that lack built-in error handling, like Change Data Capture (CDC) and polling-based sources. If your source system already has its own error handling mechanism, we recommend that you choose between using the source system's error handling or the Micro-Integration error handling—avoid enabling both at the same time. You configure error handling in the Error Handling step when you create or edit a Flow in Solace Cloud.

You can now use XML payloads in addition to JSON payloads when you create data mappings in Micro-Integration Flows. This enhancement allows you to work with data from legacy systems that use XML formats and transform it for use with modern systems, or vice versa.

When you import a payload sample, you can now upload either a well-formed JSON file or a well-formed XML file. You can then map payload fields and apply transformation functions to modify the data as it flows through your Micro-Integration. This feature supports XML-to-XML, XML-to-JSON, and JSON-to-XML transformations, giving you the flexibility to repurpose your events by choosing different content types for your source and target systems.

Performance improvements through architectural optimizations in message processing. These enhancements enable substantially higher message throughput and more efficient resource utilization, allowing for handling of larger workloads with the same infrastructure. In addition, further optimizations were done by enabling asynchronous publishing by default on Micro Integrations that support it, and disabling the default internal back-pressure for faster asynchronous publishing.

• The use of various Spring Framework technologies allows for easy configuration of the connector, advanced logging capabilities, and export of live metrics data to external monitoring solutions.
• Authentication Options: Supports both private key and basic password authentication (useful for local testing).
• The SFTP Source Key Features:
• Delimited Files: Split files based on a configurable delimiter.
• JSON Files: Split JSON files using a configurable JSONPath expression.
• XML Files: Split XML files using a configurable XPath expression.
• Filter files using configurable expressions.
• Supports for recursive processing of subdirectories.
• The SFTP Target Key Features:
• Automatic File Rotation: Automatically rotates files based on a configurable maximum file size or the number of events written.
• Dynamic File Naming: Route events dynamically to target files using event metadata/headers (via scst_targetDestination).