12.11 Harmony release notes

12.11 Harmony release

The 12.11 Harmony release is staggered based on the dates and times as listed below by component and region. For a more detailed explanation of the release cadence by component category, see the release schedule.

App Builder 4.67 and Wevo iPaaS have separate release notes.

Compilations of release notes for Production Cloud Agent Groups, Sandbox Cloud Agent Groups, and private agents are also available.

You can subscribe to maintenance notifications for web-based components at Jitterbit Trust. Locally installed components are available from the Downloads page. Docker private agent, private API gateway, and App Builder images are available at Jitterbit's Docker Hub. The end-of-life date for these components (except App Builder) is one year after the release date.

New features

Connectors

• ServiceNow v2 connector
  The ServiceNow v2 connector is now generally available. It can be used with cloud or private agents to query, create, update, or delete records in ServiceNow.

Enhancements

Agent

• Connection pooling for source and target database connections
  Agents can now reuse pooled JDBC connections for a Database connection in Studio and a Database source or target in Design Studio, instead of opening and closing a new connection for every operation. This reduces connection overhead and improves reliability under heavy concurrent load. Connection pooling is disabled by default. To enable it on a private agent, set jdbc.hikari.enabled=true in the [SourceTargetPooling] section of jitterbit.conf, then restart the agent.

Connectors

• Amazon Bedrock connector support for GPT-5.6 models
  The Amazon Bedrock Prompt and Register Tools activities now support OpenAI's GPT-5.6 model family: gpt-5.6-sol, gpt-5.6-terra, and gpt-5.6-luna. Because these models require an AWS inference profile ID rather than an on-demand model ID, select the Enter model identifier option and enter the model's inference profile ID (for example, us.openai.gpt-5.6-sol) instead of selecting the model from the List all models table.

• MCP Client Prompts and Resources activity general availability and default selection
  The MCP Client connector includes the following updates to its Prompts and Resources activities:

  • General availability: The List Resources, List Prompts, Get Prompt, and Read Resource activities are now generally available.
  • Default selection: The Choose tool, Choose prompt, and Choose resource steps of the Invoke Tools, Get Prompt, and Read Resource activities now default to the Select tool from list, Select prompt from list, and Select resource from list option, rather than the manual entry option.

• Manual entry labels standardized across connectors
  Connectors now use a consistent label for the option to manually enter an object's name, ID, or URI. Previously, this label varied by connector, using wording such as Inform..., Enter..., or Use Text Inputs.

  • Amazon S3: The Get Object, Put Object, Delete Object, List Objects, and Move Object activities specify a bucket using the Select Bucket From List or Provide S3 Bucket Manually option.
  • Cloud Datastore: The Insert Items, Query Items, Update Items, Delete Items, Delete Storage, and Get Metrics activities specify a storage name using the Provide storage name manually option.
  • Google Pub/Sub: The Get, Publish, Acknowledge, and Listener activities specify a subscription or topic using the Provide Subscription Manually or Provide Topic Manually option.
  • MCP Client: The Invoke Tools, Read Resource, and Get Prompt activities specify a tool, resource, or prompt using the Provide tool name manually, Provide resource URI manually, or Provide prompt name manually option.
  • Microsoft Azure Key Vault: The Update Vault Objects, Delete Vault Objects, and Query Vault Objects activities specify an object using the Provide object manually option.
  • Microsoft Azure Service Bus: The Send Message activity specifies a queue or topic using the Provide Queue or Topic Manually option.
  • Microsoft Teams: The Chat activity specifies a chat using the Provide Chat ID Manually option.
  • SMB: The Create Folder, Create File, Search, Update Folder, Update File, Delete Folder, Delete File, and Read File activities specify a folder using the Provide folder name manually option.
  • Slack: The Send Message activity's Provide Conversation ID Manually option and Provide Conversation ID/Channel ID field specify the conversation or channel.

Management Console

• Usage status and endpoint references on the App Registrations page
  The App Registrations page's main table has new Usage and Endpoints columns showing whether each app registration is referenced by any endpoints and, if so, by how many. The registration's details drawer has a new Endpoints usage tab listing the project, environment, connector, expiration, authorization status, and last deployed date for each referencing endpoint, along with a Go to endpoint action to open the endpoint's configuration in Studio.

Studio

• More component types in the selective import and selective transfer diff view
  The diff view for reviewing component conflicts now covers more component types:

  • Selective import: The View changes button now covers tools, operations, project variables, email notifications, connector endpoints, and connector activities, in addition to the existing script and transformation support. These additional types use a new field comparison diff view, shown as a Name, Before, and After table, alongside the existing side-by-side code diff view used for scripts and transformations.
  • Selective transfer: The View changes icon now also covers tools, email notifications, operations, project variables, and schedules, in addition to the existing script, transformation, connector endpoint, and connector activity support.

Changes

Agent

• Synchronous RunOperation call limit within While loops
  A While loop that calls RunOperation synchronously is now capped at 50 calls by default, to prevent a runaway or unbounded loop from invoking thousands of child operations. When the limit is reached, RunOperation returns false and the script continues running; the reason is available from GetLastError and is also recorded in the operation log.

  Three new keys in the [OperationEngine] section of the private agent configuration file (jitterbit.conf) control this behavior:

  • MaxSynchronousRunOperationCallsInLoop: Changes or removes the default limit.
  • MaxSynchronousRunOperationCallsInLoopOverrideAllowed: Controls whether an individual operation can override the limit using the new jitterbit.operation.max_sync_runop_calls_in_loop Jitterbit variable.
  • MaxSynchronousRunOperationCallsInLoopCustomError: Customizes the error message shown when the limit is hit.

• External entity restrictions for RunXSLT
  For security reasons, agents now block DOCTYPE declarations and external entity resolution by default when processing the RunXSLT function: XML input containing a DOCTYPE, ENTITY, or external URI reference is rejected. To allow this processing, update the corresponding key in the [XsltEngine] section of the agent configuration file (jitterbit.conf), then restart the agent.

API gateway

• User identifier length limit for API logs
  The value recorded to identify who made an API request is now limited to 256 characters, matching its underlying storage limit. A request fails with a TRIGGER_USER_TOO_LONG error if this value exceeds the length limit. To resolve this error, check which of the following applies:

  • Basic authentication with the default Logging setting: Update the security profile's User name field to 256 characters or fewer, then update the credentials in any calling application that references the previous username.
  • Custom Logging setting: Update the calling application to send a header value that is 256 characters or fewer.

Fixes

Agent

• File Share connector now substitutes a variable placed after a backslash in a path
  The File Share connector's Path field, in its connection configuration, and the FileList function called from a script, now substitute a global or project variable that immediately follows a backslash (\\) in a UNC path (for example, \\\\server\\share\\[myVariable]\\). Previously, the backslash immediately before the variable was treated as an escape character, so the literal variable name was used in the path instead of its value, causing errors such as The system cannot find the path specified.

• Design Studio field validation now honors a configured Skip Row action
  A Design Studio field validation rule configured with a Skip Row action is honored again during operation runtime. Starting with agent version 12.6, a row that should have been skipped based on a configured validation rule instead reached the target unchanged.

• Canceled operation duration now reported accurately
  When an operation is canceled after reaching its configured Operation time out, the Duration shown in the Management Console Runtime operation details table and in operation logs now reflects the actual time until cancellation, typically within a few seconds of the configured timeout value. Previously, this duration could be reported as up to twice the configured timeout value, even though the operation was canceled at the correct time.

• Multibyte filenames on Windows private agents now processed reliably
  Reading or writing a file whose name contains multibyte characters is now processed reliably on Windows private agents using File Share, FTP, Local Storage, or Temporary Storage in Studio or Design Studio.

Agent and Design Studio

• Salesforce OAuth 2.0 connection edits now persist correctly in Design Studio
  Changes to the Instance URL, Client ID, and Client secret fields of an existing Salesforce Org configured with 2-legged OAuth 2.0 client authentication are now saved before Test Salesforce Login runs. Previously, testing the connection immediately after editing these fields could validate against the previous values instead of the updated ones, returning a misleading success or failure result.

API Manager

• API health monitoring CSV download now matches the selected gateway
  Downloading the API health monitoring table as CSV on the Analytics page now returns data for the same gateway as the results displayed on screen. Previously, the download always returned data for the organization's default gateway, regardless of which gateway's data was currently selected and displayed.

Connectors

• Excel v2 connector now loads correctly on 12.x Windows private agents
  The Excel v2 connector now loads correctly on 12.x Windows private agents. Previously, testing a connection or running an operation using this connector on a 12.x Windows private agent returned an error indicating the connector was not found on the agent. To apply this fix, click Test on the connection in Studio to download the latest connector version, or use the Management Console Agents page's Action > Update connectors to force the update across the agent group. This issue remains open on Linux private agents; see Excel v2 connector fails to load in the private agent known issues.

Harmony platform

• Project deployments no longer fail during a database failover
  Deploying a project in Studio or Design Studio no longer fails, or hangs for an extended period, during a database failover. Previously, an in-progress failover or extended maintenance event could block project deployments until it completed.

• Operations that an agent can't run now fail faster
  An operation whose assigned agent reports it's unable to run the operation now transitions to Error status much more quickly. This also resolves a related issue where a large backlog of such operations competed for limited retry attempts each cycle, delaying resolution further.

• API Logs and Analytics data now recorded for older private API gateway versions
  API requests served through a private API gateway earlier than version 11.57 now generate entries in API Logs and Analytics. Previously, these entries could silently fail to appear even though the request was processed normally.

Management Console

• Environment role access count no longer becomes inaccurate after concurrent edits
  The Environment Role Access tab on the User Management page and the Role Access pane on the Environments page now stay in sync when the same role's environment access is edited from both locations at the same time. Previously, doing so could create a duplicate role-environment association, causing the environment count shown on the User Management page to no longer match the organization's actual number of active environments.

• Cloud Datastore key storage table now scrolls horizontally
  The key storage data table in a key storage's details drawer now shows a horizontal scrollbar when its columns are wider than the drawer, letting you scroll to view any columns, including Actions, that would otherwise extend past the right edge. Previously, these columns were cut off with no way to scroll to them, though they remained reachable by shift-scrolling.

Studio

• Editing certain large or deeply nested schemas no longer causes Studio to become unresponsive
  Editing a schema that is very large or deeply nested no longer causes the browser tab to become unresponsive or run out of memory when you click Edit Schema. Nodes in a schema of 5,000 or more nodes are now expanded to 2 levels deep by default, rather than 5.

Notices

Agent

• Retirement of 11.x private agent versioning
  The 11.59 / 12.3 release included the final 11.x private agent version (11.59) and the first available 12.x private agent version (12.3). Note the following regarding future releases:

  • Final 11.x version: The 11.x private agent version has reached the end of its planned development. All future enhancements, new features, and security updates will be delivered through 12.x private agents. While 11.x agents may receive rare critical fixes for production-impacting issues, no ongoing releases are planned.
  • Recommendation: We strongly recommend upgrading to 12.x private agents as soon as possible to benefit from the latest performance, security, and feature improvements.
  • Upgrade path: You can upgrade directly from 11.x to any 12.x version using our documented upgrade instructions: Windows, Linux, or Docker.

  Actions required: Plugin updates and verification of custom connectors for 12.x private agents

  • Plugin updates for 12.x private agents
    Performance and security enhancements for 12.x private agents are incompatible with the Multipart Pipeline and AWS S3 Create Plugins. If you use these plugins, user action is required as described in the upgrade instructions.
  • Verification of custom connectors for 12.x private agents
    Connectors built by a third party with the Connector SDK must undergo development changes to be compatible with 12.x private agents. Before upgrading to 12.x private agents, verify compatibility with the connector developer, or operations using those connectors will begin failing at the time of upgrade.

Agent and API gateway

• End of life for version 11.49
  As of September 18, 2026, these product versions have reached end of life and are no longer supported:

  • Private agent version 11.49
  • Private API gateway version 11.49

  We recommend that users of these versions upgrade to the latest version as soon as practicable.

Connectors

• Action required: Deprecation of OpenAI Prompt and Register Tools activities
  The OpenAI Prompt and Register Tools activities are now deprecated and no longer supported, and will be permanently removed in an upcoming release. Both were replaced in the 12.8 release by the redesigned Prompt V2 and Register Tools V2 activities, whose use of OpenAI's Responses API makes it possible to persist chat context and call registered tools on cloud agent groups, not just private agents.

  Important

  If you are using the Prompt (Deprecated) or Register Tools (Deprecated) activity in any operations, you must review your operation design and replace it with the Prompt V2 or Register Tools V2 activity as soon as possible, as the deprecated activities are no longer supported and will be removed in the future.

• Action required: Upcoming removal of deprecated Cloud Datastore Query Items activity
  In an upcoming release, the deprecated Query Items activity in the Cloud Datastore connector will be permanently removed. This activity was replaced in the 11.47 release by the redesigned Query Items activity, whose flattened response structure returns the individual fields you define in the Management Console Cloud Datastore page directly at the top level of the response.

  Important

  If you are using the deprecated Query Items activity in any operations, you must review your operation design and replace it with the redesigned Query Items activity as soon as possible. The deprecated activity is no longer supported and will be removed in a future release.