n8n 1.123.60 - Billing Fix and Quality-of-Service Improvements

The 1.123.60 update addresses a material billing concern by excluding failed workflow executions from billable execution counts. This change reduces the risk of customers being charged for transient or systemic errors and signals n8n's attention to fair usage accounting. For platform operators and vendors reselling n8n instances, the change requires careful examination of metering logic and communication to customers.

From a business perspective, billing correctness affects retention and legal exposure. Customers who discover they were charged for errored runs often escalate quickly. Platform teams must align metering definitions with contractual terms and ensure that external reporting and invoices reflect the updated logic. Additionally, teams should test edge cases: partial failures, retries, and error workflows that intentionally capture failures for diagnostics.

Operational improvements that complement this release include enhancing observability to distinguish successful, retried, and errored runs; adding labels or metadata to executions for billing reconciliation; and implementing throttling or circuit breakers to prevent cascades of failed executions from inflating counts. Where automated retry policies exist, clarify whether retries are billable and how deduplication is performed.

Actionable guidance: audit existing billing dashboards and invoices for discrepancies, update customer-facing documentation to explain the new counting rules, and implement synthetic tests to validate metering behavior. These steps preserve customer trust, reduce billing disputes, and turn a technical fix into a competitive advantage.