E08 · Recover value safely
Synthetic practice, not company performance.
One decision
Which recovery should be built first?
Run the exact query
WITH b AS (SELECT * FROM v_task WHERE ('all'='all' OR persona='all') AND ('all'='all' OR workflow='all') AND ('all'='all' OR substr(signup_at,1,7)='all') AND date(created_at)>='2026-05-01' AND date(created_at)<'2026-10-01') SELECT workflow,COUNT(*) tasks,SUM(failed_attempts>0) tasks_with_failed_attempt,SUM(failed_attempts>0 AND render_success=1) recovered_to_render,SUM(failed_attempts>0 AND confirmed_quality_use=1) recovered_to_value,SUM(attempts>1) retried,SUM(render_success=0 AND eligible=1) unfinished_eligible FROM b GROUP BY workflow;
Download SQL · Result CSV · Metabase saved question
Chart and reading
Compare tasks with failures, recovered renders and recovered useful tasks.
Challenge your recommendation
Does render recovery actually restore use?
Guardrails: All failures mature at cutoff except latest-day tasks excluded by generator; recovery-to-render differs from customer value.
Next evidence: Failure eligibility, customer intent, observation window and debit reconciliation.
PRD sections: 6, 11, 17. Open proposed PRD
Your spoken decision
State one takeaway, one caveat and one action in 30 seconds. Then stop.
Connect this finding
What this chart helps decide · Follow the connected decision · Canonical metric definitions
Optional model answer — try your own first
E08 · Recover value safely
Decision: Which recovery should be built first?
Readout: Compare tasks with failures, recovered renders and recovered useful tasks.
Actual query output (synthetic), first rows:
| workflow | tasks | tasks_with_failed_attempt | recovered_to_render | recovered_to_value | retried | unfinished_eligible |
|---|---|---|---|---|---|---|
| api_template | 390 | 44 | 12 | 2 | 13 | 32 |
| document_avatar | 373 | 54 | 10 | 3 | 11 | 44 |
| dubbing | 318 | 57 | 7 | 1 | 10 | 50 |
Model spoken answer: I would choose recovery by useful work restored, while checking duplicate charges and total retries.
Caveat/counterargument: Does render recovery actually restore use? All failures mature at cutoff except latest-day tasks excluded by generator; recovery-to-render differs from customer value.
Next evidence: Failure eligibility, customer intent, observation window and debit reconciliation.
Deliberately left out: A low retry rate presented as automatically good.