Release notes for the Jitterbit Sandbox Cloud Agent Group
Introduction
This page provides a compilation of updates for the Sandbox Cloud Agent Group. Updates to the Sandbox Cloud Agent Group are also identified on individual release pages in Release notes.
For releases not shown here, see Past Harmony releases.
Known issues
For known issues with the Sandbox Cloud Agent Group, see Known issues in Cloud agent groups.
Release notes
A subset of Harmony release updates pertaining to the Sandbox Cloud Agent Group is included below.
11.52
The 11.52 release date for the Sandbox Cloud Agent Group is by region:
| Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | November 11, 2025 (6 AM AEDT) | 
| EMEA | November 13, 2025 (1 AM CET) | 
| NA | November 13, 2025 (4 PM PST) | 
The release notes will be published on this page prior to the release.
11.51
The 11.51 release date for the Sandbox Cloud Agent Group is by region:
| Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | October 21, 2025 (6 AM AEDT) | 
| EMEA | October 22, 2025 (1 AM CEST) | 
| NA | October 22, 2025 (4 PM PDT) | 
Fixes
- Automatic canceling and re-running of stuck scheduled operations
 If an agent becomes stopped for any reason, scheduled operations assigned to it are now automatically canceled and immediately recreated on an active agent in the group. (If the agent is the only one in a group, operations eventually time out and fail.) This resolves an issue where operations could become "stuck" in the status they were in when an agent became stopped.
Changes
- 
User action required: New APAC cloud agent IPs 
 If you use APAC region cloud agents to access endpoints within your network behind a firewall, you must allow three additional IP addresses:- 16.50.32.215
- 16.51.140.139
- 16.51.180.48
 The new IPs will go into effect for the APAC Sandbox Cloud Agent Group with its 11.51 upgrade on October 21, 2025. The new IPs went into effect for the APAC Production Cloud Agent Group with its 11.48 upgrade on August 26, 2025. If you don't add these IPs, dependent integration operations will stop functioning as intended. On October 21, 2025, you may also remove the following IP addresses, which are being decommissioned: - 3.0.141.187
- 13.251.231.2
- 52.220.155.2
 For additional information, see APAC IP changes FAQ. All IP addresses that must be added to ensure communication inbound to your network from cloud agents are listed in Jitterbit allowlist (whitelist) information. 
11.50
The 11.50 release date for the Sandbox Cloud Agent Group is by region:
| 11.50 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | September 30, 2025 (4 AM AEST) | 
| EMEA | October 1, 2025 (1 AM CEST) | 
| NA | October 1, 2025 (4 PM PDT) | 
Fixes
- NetSuite Search activity configuration issue fixed
 Configuration of a NetSuite Search activity with a search type of Saved Search with result fields as output now works as expected when the account number is used in uppercase within the saved search URL. Previously, the Next button was not functioning.
Notices
- 
User action required: New APAC cloud agent IPs 
 If you use APAC region cloud agents to access endpoints within your network behind a firewall, you must allow three additional IP addresses:- 16.50.32.215
- 16.51.140.139
- 16.51.180.48
 The new IPs will go into effect for the APAC Sandbox Cloud Agent Group with its 11.51 upgrade on October 21, 2025. The new IPs went into effect for the APAC Production Cloud Agent Group with its 11.48 upgrade on August 26, 2025. If you don't add these IPs, dependent integration operations will stop functioning as intended. On October 21, 2025, you may also remove the following IP addresses, which are being decommissioned: - 3.0.141.187
- 13.251.231.2
- 52.220.155.2
 For additional information, see APAC IP changes FAQ. All IP addresses that must be added to ensure communication inbound to your network from cloud agents are listed in Jitterbit allowlist (whitelist) information. 
11.49
The 11.49 release date for the Sandbox Cloud Agent Group is by region:
| 11.49 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | September 9, 2025 (4 AM AEST) | 
| EMEA | September 10, 2025 (1 AM CEST) | 
| NA | September 10, 2025 (4 PM PDT) | 
Enhancements
- 
NetSuite connector search type for returning saved search fields as output 
 A NetSuite Search activity has a new search type, Saved Search with result fields as output, available to select in activity configuration step 2. The new search type requires agents version 11.49 or later and a deployed Suitelet script to fetch the metadata needed to limit the response schema fields.
- 
Endpoints Usage (Beta) reporting 
 The Dashboard page's Licensing vs Actual Usage tile now reports the number of licensed endpoints compared with how many unique endpoints have been used in the current month on agents 11.49 or later in a production-class environment. Unique endpoints are determined by their Endpoint unique identifier values, shown on the new Endpoints Usage (Beta) page, where you can also see month-by-month usage.Agents version 11.49 or later are required for endpoints usage reporting. To provide beta feedback, contact the Jitterbit Product Team. 
Notices
- 
User action required: New APAC cloud agent IPs 
 If you use APAC region cloud agents to access endpoints within your network behind a firewall, you must allow three additional IP addresses:- 16.50.32.215
- 16.51.140.139
- 16.51.180.48
 The new IPs will go into effect for the APAC Sandbox Cloud Agent Group with its 11.51 upgrade on October 21, 2025. The new IPs went into effect for the APAC Production Cloud Agent Group with its 11.48 upgrade on August 26, 2025. If you don't add these IPs, dependent integration operations will stop functioning as intended. On October 21, 2025, you may also remove the following IP addresses, which are being decommissioned: - 3.0.141.187
- 13.251.231.2
- 52.220.155.2
 For additional information, see APAC IP changes FAQ. All IP addresses that must be added to ensure communication inbound to your network from cloud agents are listed in Jitterbit allowlist (whitelist) information. 
11.48
The 11.48 release date for the Sandbox Cloud Agent Group is by region:
| 11.48 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | August 19, 2025 (4 AM AEST) | 
| EMEA | August 20, 2025 (1 AM CEST) | 
| NA | August 20, 2025 (4 PM PDT) | 
Notices
- 
User action required: New APAC cloud agent IPs 
 If you use APAC region cloud agents to access endpoints within your network behind a firewall, you must allow three additional IP addresses by August 26, 2025:- 16.50.32.215
- 16.51.140.139
- 16.51.180.48
 The new IPs will go into effect with the 11.48 Production Cloud Agent Group and 11.51 Sandbox Cloud Agent Group upgrades. If you don't add these IPs by August 26, 2025 for the Production Cloud Agent Group or October 21, 2025 for the Sandbox Cloud Agent Group, dependent integration operations will stop functioning as intended. On October 21, 2025, you may also remove the following IP addresses, which are being decommissioned: - 3.0.141.187
- 13.251.231.2
- 52.220.155.2
 For additional information, see APAC IP changes FAQ. All IP addresses that must be added to ensure communication inbound to your network from cloud agents are listed in Jitterbit allowlist (whitelist) information. 
11.47
The 11.47 release date for the Sandbox Cloud Agent Group is by region:
| 11.47 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | July 29, 2025 (4 AM AEST) | 
| EMEA | July 30, 2025 (1 AM CEST) | 
| NA | July 30, 2025 (4 PM PDT) | 
Enhancements
- 
Salesforce API version 64 support 
 Salesforce API version 64 is now supported for these connectors:- The Integration Studio Salesforce, Salesforce Service Cloud, and ServiceMax connectors automatically use this API version with 11.47 or later agents.
- The Design Studio Salesforce connector supports this API version with the use of both 11.47 or later agents and an 11.47 or later version of Design Studio. When both these version requirements are met, an API upgrade dialog is shown when opening existing projects using this connector.
 
Notices
- 
User action required: New APAC cloud agent IPs 
 If you use APAC region cloud agents to access endpoints within your network behind a firewall, you must allow three additional IP addresses by August 26, 2025:- 16.50.32.215
- 16.51.140.139
- 16.51.180.48
 The new IPs will go into effect with the 11.48 Production Cloud Agent Group upgrade and 11.51 Sandbox Cloud Agent Group upgrade. If you don't add these IPs by August 26, 2025 for the Production Cloud Agent Group or October 21, 2025 for the Sandbox Cloud Agent Group, dependent integration operations will stop functioning as intended. On October 21, 2025, you may also remove the following IP addresses, which are being decommissioned: - 3.0.141.187
- 13.251.231.2
- 52.220.155.2
 For additional information, see APAC IP changes FAQ. All IP addresses that must be added to ensure communication inbound to your network from cloud agents are listed in Jitterbit allowlist (whitelist) information. Important This release note was edited on August 7, 2025 to update the planned dates of APAC IP changes for the Sandbox Cloud Agent Group. The change in dates is explained in Postponed dates for SCAG in the APAC IP changes FAQ. 
11.46
The 11.46 release date for the Sandbox Cloud Agent Group is by region:
| 11.46 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | July 9, 2025 (4 AM AEST) | 
| EMEA | July 10, 2025 (1 AM CEST) | 
| NA | July 10, 2025 (4 PM PDT) | 
Fixes
- DebugBreaknow jumps from parent to child script as expected
 When running a script that calls another script containing the- DebugBreakfunction, Design Studio now jumps to the breakpoint as expected. The issue was limited to using the macOS version of Design Studio with cloud agents or Linux private agents.
11.45
The 11.45 release date for the Sandbox Cloud Agent Group is by region:
| 11.45 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | June 17, 2025 (4 AM AEST) | 
| EMEA | June 18, 2025 (1 AM CEST) | 
| NA | June 18, 2025 (4 PM PDT) | 
Enhancements
- Microsoft Entra authentication and cloud agent support for Microsoft SQL Server
 Microsoft Entra authentication is now supported with the SQL Server Microsoft JDBC driver in an Integration Studio Database connection or a Design Studio Database source or target. This driver is newly provided on cloud agents.
Fixes
- 
JSONStringifysupport for null data and reserved JSON characters
 TheJSONStringifyfunction now handles null data and reserved JSON characters such as"and\as expected.Warning If you previously implemented a workaround to escape reserved JSON characters, you must make updates to accommodate this fix or your operations dependent on this function may stop functioning as expected. 
- 
FTP files no longer have unexpected prefixed timestamps 
 In certain scenarios, files retrieved using the Integration Studio FTP connector or Design Studio FTP source no longer have unexpected timestamp prefixes requiring a workaround using the Jitterbit variablejitterbit.source.ftp.enable_regex_parser.
- 
Salesforce Bulk operations issue fixed 
 A database error has been resolved with operations that use Bulk activities provided by the Integration Studio Salesforce, Salesforce Service Cloud, or ServiceMax connectors or the Design Studio Salesforce Bulk Process Wizard.
- 
Salesforce erroneous SOAP fault fixed 
 An issue has been resolved with Salesforce operations where the operation status could report a SOAP fault when none occurred.
11.44
The 11.44 release date for the Sandbox Cloud Agent Group is by region:
| 11.44 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | May 28, 2025 (4 AM AEST) | 
| EMEA | May 29, 2025 (1 AM CEST) | 
| NA | May 29, 2025 (4 PM PDT) | 
Enhancements
- 
API system variable support for null processing 
 The Jitterbit variablejitterbit.api.response, used to set an API Manager API's response when System Variable is selected in the API configuration, now supports the processing of null values when the new Jitterbit variablejitterbit.api.response.enabled_null_supportis set totruebefore the API response variable is set.It can be used in combination with the jitterbit.scripting.hex.enable_null_supportvariable andHexToStringandBase64Decodefunctions to send a Base64-encoded PDF that contains null characters as the API response. Previously, the API variable response was truncated, which remains the default behavior.
- 
MySQL JDBC driver upgrade 
 The version of the MySQL JDBC driver that can be used by Integration Studio or Design Studio database connections is now 8.4.0.
Fixes
- Design Studio Salesforce chunking issue resolved
 Design Studio Salesforce Update operations with chunking enabled no longer fail under a unique set of circumstances.
11.43
The 11.43 release date for the Sandbox Cloud Agent Group is by region:
| 11.43 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | May 6, 2025 (4 AM AEST) | 
| EMEA | May 6-7, 2025 (1 AM CEST) | 
| NA | May 7, 2025 (4 PM PDT) | 
Fixes
- IfNulland- IsNullfunctions now have expected behavior
 When the Jitterbit variable- jitterbit.target.xml.include_nil_attributeis set to- trueupstream of the- IfNullor- IsNullfunctions, the functions will evaluate an empty string as a non-null value.
11.42
The 11.42 release date for the Sandbox Cloud Agent Group is by region:
| 11.42 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | April 15, 2025 (4 AM AEST) | 
| EMEA | April 16, 2025 (1 AM CEST) | 
| NA | April 16, 2025 (4 PM PDT) | 
Enhancements
- Support for OpenSSL 3 AES compatibility
 Jitterbit scripts in Integration Studio and Design Studio now support OpenSSL 3 AES encryption and decryption by using either the new functionsAESEncryptionEx/AESDecryptionExor by setting the new Jitterbit variablejitterbit.scripting.aes.defaulttotrueupstream of the existingAESEncryption/AESDecryptionfunctions.
11.41
The 11.41 release date for the Sandbox Cloud Agent Group is by region:
| 11.41 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | March 25, 2025 (5 AM AEDT) | 
| EMEA | March 26, 2025 (12 AM CET) | 
| NA | March 26, 2025 (4 PM PDT) | 
Enhancements
- 
NetSuite WSDL version 2025.1 support 
 Jitterbit has verified support for NetSuite WSDL version 2025.1 with the Integration Studio NetSuite connector and the Design Studio NetSuite connector.
- 
Salesforce API version 63 support 
 Salesforce API version 63 is now supported for these connectors:- 
The Integration Studio Salesforce, Salesforce Service Cloud, and ServiceMax connectors automatically use this API version with 11.41 or later agents. 
- 
The Design Studio Salesforce connector supports this API version with the use of both 11.41 or later agents and an 11.41 or later version of Design Studio. When both these version requirements are met, an API upgrade dialog is shown when opening existing projects using this connector. 
 
- 
Fixes
- Salesforce API upgrade to version 62 no longer causes transformation refresh error
 An issue has been resolved where an upgrade to Salesforce API version 62 (available with Design Studio and agent version 11.35 to 11.40) prevented Salesforce transformations from being refreshed and returned the errorFailed to parse the response. The fix requires Design Studio and agent version 11.41 or later.
11.40
The 11.40 release date for the Sandbox Cloud Agent Group is by region:
| 11.40 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | March 4, 2025 (6 AM AEDT) | 
| EMEA | March 5, 2025 (11 AM CET) | 
| NA | March 5, 2025 (4 PM PST) | 
This agent version has general internal updates.
11.39
The 11.39 release date for the Sandbox Cloud Agent Group is by region:
| 11.39 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | February 11, 2025 (6 AM AEDT) | 
| EMEA | February 12, 2025 (1 AM CET) | 
| NA | February 12, 2025 (4 PM PST) | 
Fixes
- 
CVTDatefunction no longer outputs data with empty input
 When theCVTDatefunction is used with an empty input date object or string, an erroneous output date string can no longer be returned by the function.
- 
RegExMatchfunction now works for single-number matches
 TheRegExMatchfunction now correctly validates matches of single-digit numeric strings. For example,RegExMatch("5", "(^[0-9]+$)")now returns1instead of0.
- 
FTP variable paths with a default value now work 
 When an Integration Studio FTP activity or Design Studio FTP site's Path field is configured with a default value for a global variable, the default value is now substituted as expected. Previously, it was treated as if no default value was set.
11.38
The 11.38 release date for the Sandbox Cloud Agent Group is by region:
| 11.38 Sandbox Cloud Agent Group (SCAG) | |
|---|---|
| APAC | January 28, 2025 (8 PM AEDT) | 
| EMEA | January 29, 2025 (10 AM CET) | 
| NA | January 30, 2025 (1 AM PST) | 
This agent version has general internal updates.
11.37
The 11.37 release date for the Sandbox Cloud Agent Group is by region:
| 11.37 Sandbox Cloud Agent Group (SCAG) | 11.37 SCAG patch | |
|---|---|---|
| APAC | January 7, 2025 (6 AM AEDT) | January 16, 2025 (10 PM AEDT) | 
| EMEA | January 8, 2025 (1 AM CET) | January 16, 2025 (12 PM CET) | 
| NA | January 8, 2025 (4 PM PST) | January 16, 2025 (3 AM PST) | 
Note
The 11.35 and 11.36 releases were internal.
Enhancements
- 
New Jitterbit variables 
 The following new Jitterbit variables are available to use with agents 11.37 and later:- jitterbit.scripting.hex.enable_null_support: Set this variable to- trueupstream of using the- HexToStringor- StringToHexfunctions for their conversions to support a null hex value.
- jitterbit.target.xml.include_nil_attribute: Set this variable to- trueupstream of a transformation with JSON output to output both null values and empty strings.
- jitterbit.transformation.ignore_default_value: Set this variable to- trueto ignore instances of embedded nested JSON that are being treated as default variables values when processing XSLT stylesheets, such as when using the- RunXSLTfunction.
- jitterbit.source.json.trimand- jitterbit.source.json.trim.option: Set- jitterbit.source.json.trimto- falseupstream of a transformation to preserve leading and/or trailing spaces in JSON source data. When this variable is set to- trueor not set (the default is- true), you can set- jitterbit.source.json.trim.optionto- "trim"(the default; trim both leading and trailing),- "ltrim"(trim leading), or- "rtrim"(trim trailing).
 
- 
Salesforce API version 62 support 
 Salesforce API version 62 is now supported for these connectors:- The Integration Studio Salesforce, Salesforce Service Cloud, and ServiceMax connectors automatically use this API version with 11.35 or later agents.
- The Design Studio Salesforce connector supports this API version with the use of both 11.35 or later agents and an 11.35 or later version of Design Studio. When both these version requirements are met, an API upgrade dialog is shown when opening existing projects using this connector.
 
Fixes
- 
Jitterbit AWS S3 Get plugin compatibility with TLS 1.3 
 The Jitterbit AWS S3 Get plugin (deprecated) no longer results in anInvalid SSL master secreterror due to incompatibility with TLS 1.3. This fix requires version 1.0.1.0 of this plugin, which is associated with cloud agent groups by default and can be associated with a private agent group through the Management Console Plugins page.
- 
Scheduled operations now run on the day of their end date 
 Schedules with a specified end date now execute all scheduled runs including the entire day of the specified end date.
- 
Process Engine reliability improved 
 The agent’s Process Engine service is more reliable and no longer crashes in certain circumstances.
11.34
The 11.34 release date for the Sandbox Cloud Agent Group is by region:
- APAC: October 29, 2024 (5 AM AEDT)
- EMEA: October 30, 2024 (12 AM CET)
- NA: October 30, 2024 (4 PM PDT)
Agent
- 
Automatic resolution of stuck operations 
 Operations no longer get stuck in a state where they are not actively being processed by an agent but remain reporting a Received, Pending, Running, or Cancel Requested status indefinitely. This issue occurred only with synchronous child operations.
- 
Base64Decodenow works as expected with or without padding characters
 TheBase64Decodefunction no longer returns a truncated or wrong value when the base64-encoded string does not end with=or==.
- 
Schedules now use the expected time in organizations using the override time zone setting 
 When an organization has the Override schedule agent time zone setting enabled, schedules now trigger operations at the expected time. Previously, the setting was being ignored and schedules were using the agent time zone regardless of the time zone configured in the override setting.
Past releases
For releases not shown here, see Past Harmony releases.