SLIM Release Note¶
Cloud deployment of Saturday, 29 August 2026¶
Release date: Saturday, 29 August 2026
Environments updated: slim-demo, customer-tenant
Published: 1 September 2026 (RELEASED)
At a Glance¶
This is SLIM’s largest infrastructure change since the agentic rewrite: migrations now run on dedicated infrastructure, giving every migration consistent capacity independent of application load and stronger performance at scale for larger tenants. The release also makes step-by-step the default migration mode, brings audit reporting to every migration mode, turns on diagnostic logging so support can explain a result without asking a customer to reproduce it, and moves documentation to a public site. Project data protection is stronger too: project data is automatically backed up and restored to mitigate the impact of any infrastructure failure, and migration runs now return clear, unambiguous results every time.
Highlights
Migrations run on dedicated infrastructure, with consistent capacity and reliable performance regardless of tenant size
Step-by-step is now the default and recommended migration mode, giving reviewers a checkpoint on higher-risk jobs
Design-conformance reporting is consistent across every migration mode
Support can explain a migration result without asking a customer to re-run it
Documentation now lives on a public site, updated independent of the product release cycle
Project data is automatically backed up and restored to mitigate the impact of infrastructure failure
Per-tenant visibility into AI usage cost is a standard part of the platform
Migration Reliability at Scale¶
Migration work now runs on dedicated Amazon Bedrock AgentCore infrastructure, giving every migration its own compute independent of the web application. In practice, that means consistent performance for large migrations, and a long-running migration is no longer tied to the lifespan of a single server.
The change was validated at scale across SnapLogic’s largest tenant environments. Cold starts now complete reliably in under a minute regardless of project size — including environments with tens of thousands of files.
Tenant isolation carries through the move: each customer’s compute and model usage is walled off from every other customer’s by infrastructure policy rather than configuration, so data isolation and cost attribution both hold up under the new architecture. Which backend a migration runs on is decided by the environment rather than chosen by the user, keeping the experience simple and consistent.
Safer, More Transparent Reviews¶
Step-by-step is now the default and recommended migration mode. It gives reviewers a natural checkpoint before each stage proceeds — most valuable on unfamiliar or higher-risk source jobs. Automatic mode remains available.
Design-conformance reporting is now consistent across every migration mode, giving reviewers the same audit trail regardless of how a migration runs. Automated test coverage keeps that consistency in place going forward.
Diagnostic logging is on by default for new and existing projects, so support can explain a result without asking a customer to reproduce their migration with logging enabled. It can still be turned off per project.
Step status now stays accurate throughout a migration. A finished step keeps its “Complete” badge as later steps run, and any step that doesn’t produce its required output is clearly marked “Incomplete” — giving reviewers a transparent, trustworthy status at every stage.
Protecting Customer Data¶
Project data is automatically backed up and restored to mitigate the impact of any infrastructure failure. Work is backed up as it completes, and if a project’s data ever goes missing, restoration starts automatically — customers see, at most, a brief “restoring” notice, and in the normal case won’t see anything at all, since restoration now also runs at deploy time.
Deleting a project now automatically cleans up all of its associated data, including backups and exports, keeping storage tidy and ensuring each project’s data stays cleanly separated from any other.
Cost Visibility¶
Per-tenant visibility into Bedrock (AI) usage cost is a standard part of the platform: each customer’s compute and model usage is scoped to its own cost boundary at the infrastructure level, so usage and spend can be attributed cleanly per customer without relying on manual configuration.
Documentation¶
SLIM’s user documentation has moved to a public site at docs.snaplogicslim.com, independent of the product’s release cycle, with the introduction, getting-started and projects content rewritten for the current agentic version of SLIM.
Platform Access and Stability¶
Project names are now scoped per team, giving every team full freedom over naming without conflicts from other teams’ projects.
Background Task History is now visible to every authorized user, giving teams full visibility into their migration activity.
SLIM now restarts automatically after an instance reboot, keeping the service available without manual intervention.
Authentication configuration for
slim-demoandcustomer-tenantwas aligned across environments, and short-term access was extended for Professional Services training attendees.
Fixes in This Release¶
Version |
Improvement |
|---|---|
0.1.23 |
Agentic Engine: Large-tenant migrations start up reliably, every time |
0.1.22 |
Agentic Engine: Automatic-mode retries re-run the full intended set of steps |
0.1.20 |
Agentic Engine: Generated pipelines use only expressions the platform supports, with corrected date-formatting and unique-value guidance |
0.1.20 |
Agentic Engine: Pipeline translation always uses the current translation library |
0.1.19 |
Agentic Engine: Migration runs now return clear, unambiguous results, so the next stage always works from complete output |
0.1.17 |
Agentic Engine: Long-running migrations stay accurately timed throughout |
0.1.15 |
Agentic Engine: Large migration runs handle high-volume output smoothly |
2026-07-30 |
SLIM Application: Background Task History column headers display cleanly at any width |
Upgrade Notes¶
No action is required. This release was applied in place to
slim-demoandcustomer-tenant— projects, uploads and generated output are preserved.Diagnostic logging is now on for all projects; turn it off per project if it shouldn’t retain output.
A
logs/folder will now appear in the project tree — this is expected.The Run Backend selector is gone; the backend is decided by the environment.
Documentation links now open
docs.snaplogicslim.cominstead of an in-app page.
Appendix A: Component Versions¶
Component |
Version |
Notes |
|---|---|---|
Agentic Engine runtime image |
0.1.23 |
|
AgentCore runtime image |
digest 894480f1 |
Agentic Engine 0.1.23 base, squashed to a single layer with |
SLIM application ( |
2026-08-29 |
Unversioned; |
Deployment / infrastructure ( |
2026-08-29 |
Unversioned Terraform; applied to |
Default agent model |
Claude Sonnet 5 (1M context) |
Selectable per project; Opus 4.8, Opus 4.7, Opus 4.6 and Sonnet 4.6 also offered |
Documentation site |
2026-08-28 |
|
Component versions are quoted where the component carries one. SLIM’s application and infrastructure repositories are not release-versioned, so they are identified by deployment date.
Appendix B: References¶
Source |
Identifier |
|---|---|
SLIM application |
|
Agentic migration runtime |
|
Infrastructure |
|
Bedrock cost tracking procedure |
|
Documentation site infrastructure |
|
User documentation |
|
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.