SLIM Release Note

Cloud deployment of Saturday, 12 September 2026

Release date: Saturday, 12 September 2026

Environments updated: demo, customer tenant

Published: 15 September 2026 (RELEASED)

At a Glance

Further refinement of the status reporting: a stage’s own status heading is now the last word on whether it finished, and a completed integration reads as completed even when its record sits beside the folder the reviewer is looking at. The agentic runtime gains resilience to transient provider errors, with each retry starting from a clean slate and usage totaled across every attempt, and the guarantee that delegated work stays supervised is now enforced at build time rather than trusted. The delivery path is updated too: the runtime image now comes from SnapLogic’s own private registry.

Highlights

• A stage’s status heading is authoritative: a report headed in progress is never read as finished

• A completed integration reads as completed, wherever its record resolves

• Analysis saved before 5 September is readable and appears in the analyzed-integration list

• A stage interrupted by a transient provider error is retried, from a clean slate

• A run that fails is recorded as failed, and usage is totaled across every attempt

• Delegated work cannot run unsupervised: the guarantee is asserted when the runtime image is built

• The runtime image is pulled from SnapLogic’s private registry with the environment’s credentials

• The development environment now runs modernization work on the same dedicated infrastructure as production

Status Accuracy

The previous release on 5 September made status derive from each integration’s own record. This release finishes that work at both ends — what a stage writes, and what a reviewer is shown.

• The status heading is the last word. A stage records its outcome in a Migration Status: heading, and that heading is now authoritative: where it exists, its value decides, whatever appears further down the report. Without a heading, only a line that begins with Status: counts. A per-stage status written inside a table cell, a numbered list, a quoted passage or an unspaced bullet is read as detail rather than as the verdict, so a report headed in progress is never taken for a finished one. The application and the agentic runtime carry the identical definition, so the interface and the pipeline agree on what “finished” means.

• A completed integration reads as completed. Where an integration’s display name resolved to a folder beside the one holding its output, every file check came back empty and the integration was drawn as pending even though the pipeline had accepted it as complete. The reconciled record is now consulted for completed states as well as incomplete ones, and it is derived from the same place the pipeline wrote to.

• Analysis saved before 5 September is readable again. Analysis saved through the interface before a change in the 5 September release sat at the previous location, so it went missing from the editor and the integration dropped out of the analyzed-integration list. Both locations are now read, the current one first, and nothing is moved: saves continue to write to the current location, and a name that never collided cannot pick up a stray file.

Resilience to Transient Provider Errors

A stage whose session is cut short by a transient model-provider error — a throttling response, a gateway error, an internal provider error — is now retried automatically, up to a configured number of attempts, instead of ending the run.

• Each attempt starts from a clean slate. The stage’s output directory is cleared, supervision is rebuilt and the previous attempt’s records are set aside before a retry begins, so an attempt never runs against the debris of the one before it and two partial attempts cannot combine into something that looks complete.

• A run that fails is recorded as failed. A session that ended in a provider error is reported as a failure even when the output it left behind would otherwise satisfy the completion checks, so a reviewer is never asked to approve the remains of an interrupted run.

• Usage is totaled across every attempt. Consumption is summed over all attempts rather than reported for the last one, an attempt that ends in an error still has its consumption recorded, and no attempt is counted twice — so the figures reconcile with the provider’s own.

• Retry applies where retry is the answer. An exhausted budget is not retried with a fresh one, which would have doubled the spend to reach the same limit.

Delegated Work Stays Supervised

This release makes the guarantee that a stage’s delegated work is supervised through to completion and is verifiable rather than assumed. The agent command-line tool inside the runtime image is now pinned to a known version, and the image build checks that the mechanism keeping delegated work in the foreground is still present — a future version that dropped it fails the build with an explanation instead of quietly restoring the old behavior. At run time, if delegated work is nonetheless started unsupervised, the run stops and reports that cause by name rather than continuing towards partial output.

Exports and Administration

• Deleting an export that has no archive yet. An export record created when export analysis starts, before any archive exists, could not be deleted — the attempt raised a server error. Such a record now deletes cleanly, and an export that does have an archive removes both.

• Organizations are simpler to create. An organization’s short identifier is generated from its name: it no longer appears when adding one, and is shown read-only afterwards. Help text throughout the administration pages uses neutral examples.

Delivery and Environments

• The runtime image comes from SnapLogic’s private registry. Each environment pulls the image that carries the agentic runtime using its own instance credentials, rather than a personal access token held for it. No individual’s credential sits in the path that stands an environment up, and publishing a new image is authorized by federated identity rather than by a long-lived key. A dormant administrative key in the production account is retired in the same change.

• A release cannot move backwards. Publishing refuses to proceed if the version being released is behind the newest one already published.

• The development environment matches production. It now runs modernization work on the same dedicated infrastructure as the customer-facing environments, so a change can be validated against the architecture it will meet in production. Its bare domain now redirects to the canonical address.

• Interim infrastructure retired. The environment used to prove out dedicated infrastructure ahead of 29 August has been removed, and the shared plumbing every environment depends on is now defined in infrastructure code in its own right.

Fixes in This Release

Version	Improvement
Agentic runtime 0.1.32	The runtime image is published to SnapLogic’s private registry through federated identity
Agentic runtime 0.1.31	A stage’s status heading is authoritative for whether it finished
Agentic runtime 0.1.31	Delegated work cannot run unsupervised: pinned agent tool, checked when the image is built, detected at run time
Agentic runtime 0.1.30	A stage interrupted by a transient provider error is retried, each attempt from a clean slate
Agentic runtime 0.1.30	A run that fails is recorded as failed, and usage is totaled across every attempt
Agentic runtime 0.1.30	Publishing refuses to release a version behind the newest one already published
2026-09-07	The application reads a stage’s status heading by the same definition the runtime uses
2026-09-07	A completed integration reads as completed, wherever its record resolves
2026-09-07	Analysis saved before 5 September is readable, and returns to the analyzed-integration list
2026-09-07	An export created before its archive exists can be deleted
2026-09-08	An organization’s short identifier is generated from its name; neutral examples in administration help text
2026-09-11	Each environment pulls the runtime image with its own credentials, with no personal access token in the path
2026-09-11	The development environment runs modernization work on the same dedicated infrastructure as production

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 that showed as pending while the pipeline treated it as complete shows its true state on the next visit. It does not need to be re-run.

• Analysis that disappeared from the editor or from the analyzed-integration list after 5 September is readable again with no action, and does not need to be re-entered. Saving it again writes it to the current location.

• A stage that reports its outcome in a Migration Status: heading is read from that heading. A report that carries only per-stage status lines is still accepted, provided the line begins with Status:.

• The dedicated modernization infrastructure carries the same runtime image as 29 August. The agentic runtime improvements in this release are in the runtime bundled with the application, and reach the dedicated infrastructure with its next image publish; the status, analysis, export and administration improvements are in the application and are live now.

Appendix A: Component Versions

Component	Version	Notes
Agentic runtime image	0.1.32	Base image for the SLIM application container; 0.1.30, 0.1.31 and 0.1.32 were released in this window
AgentCore runtime image	digest 24f734ee	Unchanged since 31 August; agentic runtime 0.1.25 base, squashed to a single layer
Agent tool in the runtime image	2.1.263	Newly pinned; the image build fails if the mechanism that keeps delegated work supervised is absent
SLIM application	2026-09-08	Unversioned; the demo environment tracks the main line, the customer tenant its own branch
Deployment / infrastructure	2026-09-11	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-09	docs.snaplogicslim.com (production); the 5 September release note was published here

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	8 September 2026
Agentic modernization runtime	0.1.32 (from 0.1.28 at the previous release)
Dedicated modernization infrastructure	AgentCore runtime image, digest 24f734ee (unchanged from 29 August)
Deployment / infrastructure	11 September 2026
Default agent model	Claude Sonnet 5 (1M context)
User documentation	docs.snaplogicslim.com
Previous release	2026-SEP-05

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.