Pipeline Jobs Waste
Definition
In the context of public cloud, the terms “jobs” and “pipelines” often refer to specific cloud services designed for automation and orchestration. This is a quantitative measure for understanding “jobs waste” in the context of cloud services. It quantifies the proportion of total job costs that were attributed to jobs that didn’t complete successfully (failed, errored, canceled, or timed out). To effectively use this formula, you would need: Cost data for each job: This would typically come from the billing or cost management tools provided by the cloud vendor. Status of each job: You’d need to know whether each job ended in a “Failed,” “Error,” “Canceled,” “Timed_out,” or a successful state. Failed jobs are sunk costs which represent waste to an organization. The intent is to lower your waste percentage in production.
Formula, as published
Pipeline Jobs Waste = (Failed||Error||Canceled||Timed_out) Job Cost / Total Job Cost
Calculate it
Example values to start with; replace them with yours.
From the FinOps Foundation
More Usage Optimization KPIs
Definition and formula: Pipeline Jobs Waste, FinOps KPI library, FinOps Foundation, licensed CC BY 4.0, read 16 Oct 2026. Changed: HTML removed, dashes and British spellings changed, formula split from its data sources and examples. The calculator and the notes are Finitizer’s.
Measured once, a KPI is a number. Tracked daily, it is a practice.
Finitizer computes the KPIs your billing data supports every day, by team and product, across AWS and Google Cloud.
See how Finitizer works