Resolved Issues in 26.30.2
Issue | Fix Description |
|---|---|
E-141980 | Fixed Bulk Update Audit Logging Audit log events for bulk update actions performed by service accounts in subdomain tenants may not appear in the application log even though the actions are processed. This update ensures that these events are logged correctly, improving audit visibility and investigative efforts. |
E-141575 | Intermittent 403 Errors Resolved API requests that retrieve audit event data with an API key sometimes return a 403 Forbidden error intermittently, even when the key has the required permissions. This release fixes the authorization handling so audit event API access remains consistent and reliable. |
E-141226 | Policy Notification Timing Fixed Policy notifications no longer send before a new enforcement point policy is written to storage. This prevents early policy fetch attempts and avoids unnecessary recomputation or retries during startup or policy updates. |
E-140602 | View Inherited Rules Link Fixed In Cloud policy reports, the View inherited rules link now opens and displays inherited rules correctly when you select it. This restores visibility into inherited policy rules so you can confirm what traffic is allowed or blocked. |
E-132333 | Cluster Matching Improvement Traffic flow processing can incorrectly associate source or destination workloads with the wrong Kubernetes cluster when multiple clusters use overlapping network ranges, making activity appear as cross-cluster traffic. The system now caches the cluster reference along with workload information and prioritizes matching workloads within the same cluster to provide accurate cluster attribution in flow records. |
E-138794 | |
E-136326 |