Resolved Issues in Release 25.31
These release notes describe the new features, enhancements, resolved issues, and known issues for this release.
Resolved Issues
Issue | Fix Description |
---|---|
E-128193 | Enhanced Rule Search Accuracy in ruleset_overlapping_rule_search An omission was revealed in the ruleset_overlapping_rule_search call, lacking the addition of exclude_rules_not_resolving_to_ruleset_scope_actors=true in the URL. This exclusion led to conflicting rules not being filtered out, resulting in the retrieval of two conflicting rules instead of none. By rectifying this URL parameter oversight, scopes are now properly verified, ensuring the elimination of conflicting rules within the search results for improved accuracy. |
E-128086 | Refined Labeling Process for Cloud Resources An update has been implemented to ensure that cloud resources are no longer included in the resources picked up for labeling by default when label rules are applied. This refinement streamlines the labeling process, offering more precise control over resource identification within the cloud environment. |
E-128073 | API sometimes omits byteIn and byteOut fields In UC, the API omits byteIn and byteOut fields when there is no data, whereas in regular SaaS Core, the API returns these fields with a value of 0. This inconsistency leads to UI errors in UC during byte aggregation. Resolution: A UI fix has been added to default missing byteIn and byteOut values to 0. This will resolve the issue and ensure correct behavior when aggregating connections. In UC, the API omits byteIn and byteOut fields when there is no data, whereas in regular SAAS core, the API returns these fields with a value of 0. This inconsistency causes UI errors in UC when it tries to aggregate the bytes. The added UI fix will resolve the issue and ensure the byteIn and byteOut functions work correctly with aggregating connections. |
E-128016 | Mitigated Rate Limiting with Consolidated Endpoint Calls The issue was resolved by replacing multiple endpoint calls with a single new endpoint call. The system anticipates reducing rate-limiting concerns, enhancing overall performance, and operational efficiency. |