Data Integration Connector What's New > October 2025 > Changed behavior
  

Changed behavior

The October 2025 release includes changes in behavior for the following connectors.

IBM MQ Connector

Effective in this release, when you run an IBM MQ mapping task to write message data to queues in real time and a fatal error occurs in the IBM MQ target, the Secure Agent terminates the mapping task and stops writing message data to queues in IBM MQ.
Previously, even if a fatal error occurred in the IBM MQ target, the Secure Agent did not terminate the mapping task and continued to write message data to queues.
If you want to retain the previous behavior, set the MQFallbackToOldWriter custom property value to true in the Secure Agent properties.

JDBC V2 Connector

Effective in this release, when you create a target table at runtime, the values you specify for the Table Name and Schema Name target advanced properties are honored.
Previously, these values were ignored.

Marketo REST Connector

Effective in this release, when Marketo REST Connector passes access token to authenticate the Marketo service, the access token is passed using the authorization header.
Previously, the access token was passed using the query parameter.

Marketo V3 Connector

Effective in this release, when Marketo V3 Connector passes access token to authenticate the Marketo service, the access token is passed using the authorization header.
Previously, the access token was passed using the query parameter.

Microsoft Azure Data Lake Storage Gen2 Connector

Effective in this release, when you run a mapping to read from files of the Delta file format, you cannot use directory read, recursive directory read, or wildcard characters. You cannot use recursive directory read or wildcard characters in a mapping in advanced mode when you read from files of the Delta file format. The mappings fail with a validation error.
Previously, these mappings ran successfully without errors.