2025-12-01 Release

General Enhancements

• Flow Search in Custom Processors – Added a new executionSearchByPartner() helper that lets custom processors search for related flow executions within the same organization, making it easier to combine data from multiple flows in a single automation.  You can find additional documentation of this new function in our open source library of custom processors at https://github.com/chain-io/custom-processor-examples/blob/main/EXECUTION_SEARCH.md
  
  
• Linked Executions Experience – Updated the Linked Executions popup to use clear buttons instead of inline text links, improving readability and making it easier to navigate between related runs.
  
  
• Flow Execution Progress Indicator – Improved the auto-refresh behavior and added clearer visual feedback on the flow execution details page so users can see when the page is updating and avoid unnecessary manual refreshes.
  
  
• File API - APIs for Flow Outputs  – The Chain.io File API lets you deliver files from a Chain.io Flow to a secure, Chain.io-hosted data store and make those files available to your trading partners through a simple HTTPS GET request. It is designed for cases where you need to expose structured data or documents through a lightweight API without standing up infrastructure.
  
  
• Email as a Source for Send Flows – All send flows can now use email as a source, enabling processing of email attachments across more integrations.
  
  
• Output File Processing Order – Updated the order of operations for output files so that the output map runs first, then any post processors, and finally the output file rename. A legacy flag is available for customers who need to preserve the previous behavior and has been applied to all flows deployed before the change in behavior.

Adapter Enhancements

• EDI 997 ACK Configuration – Added a configuration option to control the ISA14 / UNB09 ACK requested flag separately from whether Chain.io expects to process 997 acknowledgements, improving compatibility with trading partners and existing EDI setups
  
  
• Gnosis Freight Shipment Registration – Added an official adapter to register shipments in Gnosis Freight, including logic to intelligently select containers based on consolidation scenarios and support for writing to custom columns via the Gnosis API.
  
  
• CargoWise Milestone Receive Flow – Extended the Receive Milestone flow type to support the CW1 XUS OC format so customers can register and update milestones using shipment as well as event xml format.
  
  
• AI Checks - Expanded maximum response length to support very large shipments with multiple checks.

General Bugfixes

• AI Shipment Checks on Multiple Shipments – Resolved a bug where AI Shipment Checks stopped after the first shipment with an error. The flow now evaluates all shipments and reports results across the full set.
  
  
• AI Prompt Length Validation – Improved error handling for very long prompts sent to AI custom processors so users receive clear feedback in the UI instead of silent failures.

Adapter Bugfixes

• CargoWise eAdaptor Next CSR Handling – Fixed an issue in the CargoWise eAdaptor Next setup flow where CSRs using certain encryption parameters could fail without clear diagnostics. CSRs are now validated more robustly and provide better feedback.
  
  
• CargoWise Native Product Description Mapping – Corrected the mapping for product descriptions in the CargoWise native product adapter so description fields from the canonical payload are consistently populated in CW1.
  
  
• EDI 997 Rejected ACK Filenames – Aligned 997 rejected acknowledgement filenames with the original inbound file names to maintain compatibility with existing downstream processes.
  
  
• Chain.io ASN EDI JSON Date Handling – Fixed a crash in the Chain.io ASN EDI JSON adapter when date values were missing from the input JSON so flows can continue processing even when dates are absent.