SLIM Release Note¶
Cloud deployment of Saturday, 5 September 2026¶
Release date: Saturday, 5 September 2026
Environments updated: demo, customer tenant
Published: 9 September 2026 (RELEASED)
At a Glance¶
Where 29 August moved modernization work onto dedicated infrastructure, this release refines the accuracy of what that work reports. Status is now derived from each integration’s own record in every case, so a completed integration reads as complete and a completed stage carries forward into the one that follows. Retrying a stage re-runs it, a platform update takes effect on projects that are already open, and a project is protected from edits while a stage is running. The largest environments gain a responsive project list, and generated pipelines carry refined field-mapping guidance for lookup-style snaps.
Highlights
Completed integrations read as complete, whatever they are named
A completed stage’s output carries forward into the next stage
Retrying pipeline generation re-runs the intended stages
A platform update takes effect on projects already in progress, as well as new ones
Work in progress is protected: editing, selection and upload are locked while a stage runs
The project list stays responsive in the largest environments
Generated pipelines map fields correctly after lookup-style snaps
Status Accuracy¶
Status is now derived from each integration’s own working record in every case, so the state a reviewer sees is the state the run reached. Three refinements contribute.
An integration’s name no longer overlaps SLIM’s working folders. Status is matched against the integration’s own folder, so a name containing a word SLIM also uses for its working folders — analysis, logs, notes, tests — resolves to the integration. A name that begins with an underscore resolves to its own folder too.
Completion is recognized however a stage words it. A stage that opens its report with “Status: Complete, with flagged gaps” is read as complete: markers now match regardless of capitalization or formatting, and the application and the runtime read them identically, so both describe a project the same way.
An unnamed or unusually named integration resolves to its own record. A missing or punctuation-only name is now handled explicitly rather than matched against the folders available.
Retries and Platform Updates¶
Retrying pipeline generation re-runs the intended stages. A retry now queues those stages to run again, rather than reporting on the output already present, and does so consistently on both the application and the runtime side.
A platform update takes effect on projects already open. A project’s session now rolls over to the new version of the modernization runtime as soon as that version is live, rather than at the end of the session’s lifetime, while keeping each project’s activity grouped for support.
Delegated Work Runs to Completion¶
A stage delegates parts of its work, and that delegated work is now supervised through to completion before the stage reports back. The runtime enforces the supervision itself rather than relying on instructions being followed, so the output a stage reports — generated files, test suites — is complete when the next stage receives it.
Protection While a Stage Runs¶
Editing instructions or analysis, adding, retagging or deleting supporting documents, changing the integration selection and extracting assets are all disabled while any stage is running — in both automatic and step-by-step mode, and on every page, not only the page the run started from. Each locked control explains itself (“Locked while … is running”), and a page whose own stage is idle shows which stage is busy.
The same rule is enforced behind the interface, so a browser tab left open from before a run cannot write into a project mid-stage. Save Selection surfaces that as a Project Busy notice, and a refused edit keeps the editor open with the text intact.
Responsive in the Largest Environments¶
The project list now reads each project’s statistics from a cache — refreshed as work completes, and pre-computed at deployment — rather than recomputing them from every file the project has produced on each request. Environments with many large projects load promptly, including on the first visit after an update.
Enhanced Pipeline Generation¶
Field mapping after lookup-style snaps. Lookup, Select and Execute snaps return their own output at the top level and nest the incoming document beneath it. Generation now maps through that nesting, so fields read immediately after one of these snaps resolve to their values, and the rule is documented where the generator reads it.
A single current copy of the translation libraries. The runtime image now resolves one current copy of its translation dependency, so generated pipelines are produced against the current library.
Documentation and Environments¶
Release notes are now published on the documentation site alongside the product documentation at
docs.snaplogicslim.com, and the site’s presentation follows SnapLogic’s design system.The documentation site’s publishing access is now defined in infrastructure code, keeping it consistent across infrastructure changes.
A dedicated development environment, on a managed database, is available for validating changes ahead of a customer-facing release.
The procedure for shipping a new modernization runtime image is documented as a runbook, including the steps that verify a deploy has reached running projects.
Fixes in This Release¶
Version |
Improvement |
|---|---|
Agentic runtime 0.1.28 |
Generated pipelines map fields correctly after Lookup, Select and Execute snaps |
Agentic runtime 0.1.27 |
A single, current copy of the translation libraries in the runtime image |
Agentic runtime 0.1.26 |
Completion is recognized however a stage words its status |
Agentic runtime 0.1.26 |
Delegated work is supervised through to completion before a stage reports back |
Agentic runtime 0.1.25 |
Retrying pipeline generation re-runs the intended stages |
2026-09-05 |
Completed integrations read as complete, whatever they are named |
2026-09-02 |
A project is protected from edits, uploads and selection changes while a stage runs |
2026-08-31 |
The project list stays responsive in the largest environments |
2026-08-31 |
A platform update takes effect on projects already in progress |
Upgrade Notes¶
No action is required. This release was applied in place to the demo and customer tenant environments — projects, uploads and generated output are preserved.
An integration whose status read as unfinished shows its current status on the next visit. It does not need to be re-run.
A project that paused at a stage boundary can be continued from that point; the completed stage does not need to run again.
Editing, upload and selection controls are intentionally unavailable while a stage is running, and return when it finishes.
The dedicated modernization infrastructure is unchanged from 29 August; this release updates the application and the runtime bundled with it.
Appendix A: Component Versions¶
Component |
Version |
Notes |
|---|---|---|
Agentic runtime image |
0.1.28 |
Base image for the SLIM application container |
AgentCore runtime image |
digest 24f734ee |
Unchanged since 29 August; agentic runtime 0.1.25 base, squashed to a single layer |
SLIM application |
2026-09-05 |
Unversioned; the demo environment tracks the main line, the customer tenant its own branch |
Deployment / infrastructure |
2026-09-02 |
Unversioned Terraform; most recent change applied ahead of this release |
Default agent model |
Claude Sonnet 5 (1M context) |
Unchanged; selectable per project, with Opus 4.8, Opus 4.7, Opus 4.6 and Sonnet 4.6 also offered |
Documentation site |
2026-09-03 |
|
Component versions are quoted where the component carries one. SLIM’s application and infrastructure are not release-versioned, so they are identified by deployment date.
Appendix B: References¶
Source |
Identifier |
|---|---|
SLIM application |
5 September 2026 |
Agentic modernization runtime |
0.1.28 |
Dedicated modernization infrastructure |
AgentCore runtime image, digest 24f734ee (unchanged from 29 August) |
Deployment / infrastructure |
2 September 2026 |
Default agent model |
Claude Sonnet 5 (1M context) |
User documentation |
|
Previous release |
SnapLogic Intelligent Modernizer. Copyright © 2026 SnapLogic Inc. All rights reserved. SnapLogic and the SnapLogic logo are trademarks or registered trademarks of SnapLogic Inc. All other trademarks are the property of their respective owners.