Conceptual
Login

Telling a Retryable Failure Apart From One That Will Never Succeed

This is the fork every other failure-handling node in the curation branches from: backoff and retry budgets apply only to the retryable class, and the dead-letter path exists only for the terminal class. The outcome's core promise is that a record is not lost, and the two ways to lose one are dropping a transient failure and infinitely retrying a permanent one. It is the smallest node that makes both mistakes visible, and it is testable at Apply level with nothing but a list of error strings.