Changes to Default Behavior in Strata Cloud Manager
Focus
Focus
Strata Cloud Manager

Changes to Default Behavior in Strata Cloud Manager

Table of Contents

Changes to Default Behavior in Strata Cloud Manager

Changes to the default behavior, in Strata Cloud Manager.
The following table details the changes in default behavior in Strata Cloud Manager.
FeatureReleaseChange
Non-recurring schedules
Strata Cloud Manager Release 2026.r3.0
When you add a time slot to an existing non-recurring schedule in Strata Cloud Manager, each time slot now retains its original start and end times when additional time slots are added.
In previous releases, adding a time slot to an existing non-recurring schedule overwrote the start and end times of the previously configured time slot with the current system date and time.
Dynamic Address Groups
Strata Cloud Manager 2026.r2.2
When you create a Dynamic Address Group, Zero Trust Network Access (ZTNA) Connector Tags now populate automatically via the API.
In previous releases, ZTNA Connector Tags did not populate when creating a Dynamic Address Group. The API returned a dependency error, and tags had to be entered manually.
Object Cloning
Strata Cloud Manager 2026.r2.0
In Strata Cloud Manager, configuration objects are organized in a folder hierarchy. Objects defined at higher levels are automatically inherited by all folders below them. When you clone an object to a child folder, you create a copy that can be customized for that level.
When you clone a configuration object from a parent folder or snippet to a child folder in Strata Cloud Manager Release 2.0, the system now automatically appends a -1 suffix to the cloned copy. For example, cloning an address object named blocked-ips creates blocked-ips-1 in the child folder instead of blocked-ips.
In previous releases, cloning an object with the same name as the parent object would silently override the inherited object, breaking inheritance and preventing security updates from flowing down to child folders. The new behavior preserves inheritance by default. If you intentionally want to override an inherited object, you must explicitly rename the cloned copy to match the parent object name. This ensures that overrides are always deliberate, not accidental.