diff --git a/content/docs/learn/typed-errors/working-with-typed-errors.md b/content/docs/learn/typed-errors/working-with-typed-errors.md
index 020e940a..05e778fa 100644
--- a/content/docs/learn/typed-errors/working-with-typed-errors.md
+++ b/content/docs/learn/typed-errors/working-with-typed-errors.md
@@ -426,6 +426,12 @@ fun problematic(n: Int): Either<Problem, Int?> =
 
 :::
 
+::: info Tracing the origin of a raise
+
+As projects grow in size, raised errors propagate through the call stack. To make debugging easier, Arrow provides a way to trace calls to `raise` and `bind`: [see Raise.traced](https://apidocs.arrow-kt.io/arrow-core/arrow.core.raise/traced.html).
+
+:::
+
 ## Recovering from typed errors
 
 We've already hinted this distinction above, but with working with type errors it's important to distinguish between two kinds of _problems_ that may arise: