Trailblazer 2.1's tracing renders the actual flow taken through a nested activity, highlighting which step failed and — for collections — which item caused the error. Nick Sutterer credits it with saving him significant time while building Reform 3, calling it '5–10 years ahead of Ruby' stack traces.