[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-task-success-rate::en":3,"gloss-cluster-task-success-rate::en":23,"gloss-next-task-success-rate::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"task-success-rate","analytics","Task Success Rate","Task success rate is the share of attempted tasks an automated system completed correctly, end to end. It is the headline number for anything agentic, and almost every disagreement about it is really a disagreement about the denominator and about who decides what counts as correct.\n\nThe denominator is where most of the inflation happens. A rate computed over the tasks the system chose to attempt excludes everything it declined, abandoned, or never recognised as a task, and those are exactly the hard cases. A rate computed over everything that arrived is a much less flattering number and a much more useful one. If both are reported, the gap between them is itself informative: it is the share of the problem the system currently does not touch.\n\nWho judges is the second question. Self-assessment is the weakest option, because a system that misunderstood the task will usually also misjudge whether it completed it. Checkable criteria are better where the task allows them — a test that passes, a record that reconciles, a value that matches a known answer. Human review is expensive and therefore usually sampled, which is fine as long as the sample is random rather than the cases somebody happened to look at.\n\nPartial completion has to be handled deliberately or it will be handled accidentally. A task that got most of the way and stopped cleanly is a different outcome from one that finished with a wrong result, and both are different from one that stopped halfway having already changed something. Collapsing all three into failure loses the distinction that matters operationally; counting the first as success flatters the system.\n\nThe rate is a trend, not a fact about tomorrow. It moves when the model changes, when the prompt changes, when a tool starts returning different data, and when the incoming mix of requests shifts — and the last of those causes more unexplained drops than the first three. A success rate is only interpretable next to the distribution of tasks it was measured on.","Task success rate is the share of tasks completed correctly end to end. Most disputes about it are really about the denominator and who judges correctness.",null,[11,14,17,20],{"slug":12,"name":13},"agent-trajectory","Agent Trajectory",{"slug":15,"name":16},"eval-harness","Eval Harness",{"slug":18,"name":19},"guardrail-metric","Guardrail Metric",{"slug":21,"name":22},"offline-evaluation","Offline Evaluation",[24,28,31,34,37,40,44,47,50,53,56,57],{"slug":25,"category":5,"name":26,"updated_at":27},"ab-testing","A\u002FB Testing","2026-09-08T21:32:36+00:00",{"slug":29,"category":5,"name":30,"updated_at":27},"active-user","Active User (DAU, WAU, MAU)",{"slug":32,"category":5,"name":33,"updated_at":27},"autocapture","Autocapture",{"slug":35,"category":5,"name":36,"updated_at":27},"cost-per-resolution","Cost per Resolution",{"slug":38,"category":5,"name":39,"updated_at":27},"customer-data-platform","Customer Data Platform (CDP)",{"slug":41,"category":5,"name":42,"updated_at":43},"data-sampling","Data Sampling","2026-09-08T21:32:37+00:00",{"slug":45,"category":5,"name":46,"updated_at":27},"deflection-rate","Deflection Rate",{"slug":48,"category":5,"name":49,"updated_at":43},"double-counting","Double Counting",{"slug":51,"category":5,"name":52,"updated_at":43},"feedback-signal","Feedback Signal",{"slug":54,"category":5,"name":55,"updated_at":43},"goodharts-law","Goodhart's Law",{"slug":18,"category":5,"name":19,"updated_at":27},{"slug":58,"category":5,"name":59,"updated_at":27},"identity-resolution","Identity Resolution"]