To use the SnapLogic platform features, enhancements, and fixes in the new Snaplex version, ensure that your Snaplex nodes are upgraded to version Enhancements include:
|
We use some third-party subprocessors to deliver services to our SnapLogic customers. For updates and details about the subprocessors and purpose of processing, refer to https://www.snaplogic.com/privacy-subprocessors.
We use some third-party subprocessors to deliver services to our SnapLogic customers. For updates and details about the subprocessors and purpose of processing, refer to https://www.snaplogic.com/privacy-subprocessors.
The pipeline execution records on the API metrics page in Monitor now provide the same information available under the API tab in Dashboard.
You can now create custom AutoSync endpoints with the AutoSync SDK. Start your project with a Maven archetype. Learn more.
The documentation now describes what happens during synchronization when a record has been deleted from the source since the last synchronization.
The enforcement of restricted file extensions is improved for the File upload operation in Classic Manager. The Upload file wizard now verifies (where possible) that the file content is permitted, as well as checks if the file extension is allowed. When you try to upload an unsupported file type, the operation fails with an error.
Triggered Tasks on projects created after the 4.40 release now display the Cloud URL on the Tasks Details page.
Sharing feedback on the documentation is simpler with a new feedback button on the pages of the new doc portal. Your input helps us improve our content.
The following pages are migrated to SnapLogic Documentation from the legacy documentation site:
You can view the full list of articles migrated to docs.snaplogic.com from the legacy documentation site or visit https://docs.snaplogic.com/to view all content available on the new site. |
Upcoming behavior change: Likely in the April release, you will not be able to open the Dashboard from the tab. Instead, a Monitor tab will be available when you are in Designer or Classic Manager. Until the Dashboard is completely replaced by Monitor, you will be able to open it from the waffle menu.
Upcoming behavior change: Likely in the April release, you will not be able to open the Dashboard from the tab. Instead, a Monitor tab will be available when you are in Designer or Classic Manager. Until the Dashboard is completely replaced by Monitor, you will be able to open it from the waffle menu.
You can now view an alert in the Activity log in Classic and Admin Manager when a pipeline terminates because of excessive memory consumption. You need to update your Snaplex to this release version. This alert displays the pipeline's name, path, and error details. Learn more.
Minimum Java Version Supported SnapLogic installers come with |
The Snaps mentioned in this section are deployed in the Latest set of Snap Packs. To access the latest features, an Environment admin must select the Snap Pack version in Classic Manager or Admin Manager. |
The REST Snap Pack from the Core Snap Pack will be deprecated in phases and will be replaced with the HTTP Client Snap.
Phase 1: February 11, 2025 GA release:
Starting on February 11, 2025, all REST Snaps are marked with the [Deprecated] label. SnapLogic will continue fixing any reported bugs.
Phase 2: August 13, 2025 GA release:
REST Snaps will not be available to add in Designer to existing and new pipelines. However, you can edit existing pipelines using REST Snaps, which will continue to execute as usual.
The REST Snap Pack from the Core Snap Pack will be deprecated in phases and will be replaced with the HTTP Client Snap.
Phase 1: February 11, 2025 GA release:
Starting on February 11, 2025, all REST Snaps are marked with the [Deprecated] label. SnapLogic will continue fixing any reported bugs.
Phase 2: August 13, 2025 GA release:
REST Snaps will not be available to add in Designer to existing and new pipelines. However, you can edit existing pipelines using REST Snaps, which will continue to execute as usual.
Improved thread resource management in the File Poller Snap.
Enhanced the GraphQL Client Snap to support a pagination interval that enables you to use the APIs with rate limits.
Enhanced the GraphQL Client Snap to support expressions (pipeline and upstream parameters) for the Query, Has additional page path and Next cursor path fields that enable you to dynamically pass values to the Snap. This feature allows you to decrease development and maintenance costs and increase flexibility. This has resulted in specific behavior changes.
Enhanced the Databricks Account to support M2M authentication, allowing secure connections using a Client ID and Client secret. The basic authentication for Databricks using a username and password is no longer supported since July 10, 2024.
Enhanced the Kafka OAuth2 Account to support SASL extensions through Advanced properties using OAuth/OIDC.
LDAP:
Upgraded the Apache LDAP API library from v1.0.0 to v2.1.7.
Upgraded the Spring Framework from v5.3.33 to v5.3.39.
Upgraded the amqp-client library from v5.0.0 to v5.25.0.
Updated the Apache POI library from v4.1.2 to v5.2.5 in the Excel Parser Snap.
Improved the OAuth2 account token auto-refresh process in the SnapLogic Platform by adding a mechanism that marks accounts as stale after 18 failures (applicable only for accounts with auto-refresh functionality). You can now configure notification settings to receive emails and Slack messages for stale accounts. Learn more.
When a child pipeline with a mix of ELT and Standard-mode Snaps is run manually, the parent pipeline execution encounters the following error message in the Designer and remains in the prepared state instead of failing:ELT and Standard Mode Snaps cannot be combined in a single pipeline
You might not easily identify the child pipeline causing the issue because its name with mixed Snaps isn’t clear from the error message. In contrast, when a standalone pipeline with ELT and Standard-mode Snaps (not a parent-child) is manually run, the pipeline execution errors out and doesn’t display in the dashboard at all.
Workaround: Run the pipelines as a Scheduled Task.
API Suite (GraphQL Client Snap):
The Snap now retries 401 responses by reloading the account between attempts. If the maximum number of attempts is exhausted and the response still contains a 401, the Snap stops the execution instead of writing to the error view because the error is now unrecoverable.
The validation for the Variable name and Cursor variable name fields against variable names parsed from the query is now done in the document processing stage.
For Variable name and Cursor variable name suggestible fields, a warning message is displayed if the suggested variable names cannot be generated. This happens when the Query setting uses upstream parameters in its expression and the query cannot be evaluated during the suggestion stage.
Has additional page path, Next cursor path, and Cursor variable name will no longer produce configuration errors that stop Snap execution for validation issues, such as missing or invalid values, because they are now evaluated during document processing and the values may differ between input documents. These will now produce Snap data errors that write documents to the error view, and the Snap continues to process additional input documents.
When the Query setting is expression-enabled, there can be potential syntax errors, because the expression text that is carried over can cause the following syntax issues in the interactive builder:
When the query is copied from the Snap to the query builder, it remains in expression format (for example, ${variableName}) instead of being converted into valid GraphQL syntax.
As the expression isn’t evaluated before being passed into the query builder, the UI takes raw expressions instead of actual query values. Evaluation happens later.