n8n 2.30.4 - Decoupling Execution Visibility from Licensing Controls

The 2.30.4 patch addresses a deployment and access-control nuance by decoupling the visibility of execution logs from the sharing license feature. Previously, execution visibility behavior was inadvertently linked to licensing toggles, which could cause inconsistent access for operators and auditors. The decoupling ensures administrators can manage execution visibility independently from feature-licensing concerns.

From a business perspective, execution visibility is fundamental for observability, incident response, and compliance. When visibility settings are unintentionally gated by license features, teams can experience blind spots that obstruct troubleshooting and audit trails. This fix restores a predictable access model, aligning system behavior with expectations for governance and operational transparency.

Practically, platform owners should review role and permission mappings after upgrading. Ensure audit and SRE teams can access execution history as needed, and that commercial license settings remain a business-policy control rather than an access control lever. If your organization used workarounds to surface executions (for example, logging integrations or custom exports), evaluate whether those are still necessary under the corrected behavior.

Recommended next steps: (1) schedule the patch for staging and validate that execution logs are visible to the correct roles; (2) update documentation and runbooks to distinguish licensing from visibility controls; and (3) monitor support and audit workflows for any residual confusion among teams previously affected by the coupling.