10.17 Release Notes (with behavior changes) (Preview)¶
Attention
Content on this page is available in advance of the completion of the 10.17 release, which is currently either pending or in progress and is scheduled for completion on May 12 (subject to change).
Features, updates, or behavior changes described on this page might not be available in your accounts until the release is complete.
For updates to these release notes, see Release notes change log.
Behavior change bundles¶
This release contains the following behavior change bundles:
Bundle Name |
Status in this Release |
Previous Status |
|---|---|---|
Disabled by default; admins can enable for testing |
N/A (introduced in this release) |
|
Enabled by default; admins can disable for opt-out |
Disabled by default |
|
Generally enabled; admins can no longer enable/disable |
Enabled by default |
The status for each bundle will change again in the following behavior change release, planned for June 2026; however, this schedule is subject to change.
For more information about bundle statuses and how they may impact your accounts, see About Behavior Changes.
Data integration updates¶
Openflow BYOC: per-runtime cost attribution in Account Usage views¶
Openflow BYOC credit consumption is now attributable to individual runtimes. Two changes support this:
The OPENFLOW_USAGE_HISTORY view in the ACCOUNT_USAGE schema now includes a
RUNTIME_NAMEcolumn with the name of the runtime that incurred the credit usage.The METERING_HISTORY view in the ACCOUNT_USAGE schema now populates
ENTITY_TYPEandNAMEfor rows whereSERVICE_TYPE = 'OPENFLOW_COMPUTE_BYOC'.ENTITY_TYPEreturnsOPENFLOW_RUNTIMEfor these rows, andNAMEreturns the runtime name. Previously, both columns returned NULL for all Openflow service types.
Release notes change log¶
Announcement |
Update |
Date |
|---|---|---|
Release notes |
Initial publication (preview) |
May 8, 2026 |