Snowpark Container Services job service: Retention time increase (Preview)¶
Attention
This behavior change is in the 2026_01 bundle.
For the current status of the bundle, refer to Bundle history.
When this behavior change bundle is enabled, Snowpark Container Services changes how block volumes are deleted:
- Before the change:
When you delete a block volume, no snapshots are automatically created before the block volume is deleted, and no billable events related to snapshots are automatically created during volume deletion.
- After the change:
When you delete a block volume by using any of the following commands, Snowflake first creates snapshots for the block volume, and then later deletes the snapshots:
DROP SERVICE <service-name> FORCE
ALTER COMPUTE POOL <compute-pool-name> STOP ALL
ALTER SERVICE <service-name> RESTORE VOLUME <volume-name> FROM SNAPSHOT
Snowflake assigns a snapshot name in this format:
SYS_BACKUP_ON_DELETEstring_timestamp. These snapshots have a default retention period of seven days, after which Snowflake drops the snapshots. You are billed for these snapshots. This feature protects you from accidentally deleting block volumes.Note
This change doesn’t apply to block volumes that are used by job services.
You can opt-out of this change by setting the
snapshotOnDeleteoption tofalsein the service specification:volumes: # optional volume list - name: <name> source: local | stage | memory | block size: <bytes-of-storage> # specify if memory or block is the volume source uid: <UID-value> # optional, only for stage volumes gid: <GID-value> # optional, only for stage volumes blockConfig: # optional initialContents: fromSnapshot: <snapshot-name> iops: <number-of-operations> throughput: <MiB-per-second> encryption: SNOWFLAKE_SSE | SNOWFLAKE_FULL snapshotOnDelete: true # defaults true for services and false for jobs, false to opt-out snapshotDeleteAfter: (<hours>h)|(<days>d) # defaults to 7 days
Ref: 2206