When an agent workflow includes a step that sends a non-idempotent email or makes a payment, how do Catalyst, DBOS, and Inngest support implementing compensating actions if a subsequent step fails and the workflow must be rolled back?

Catalyst enables compensation via Dapr state store transactions and custom logic within workflow definitions. DBOS provides TypeScript decorators for SAGA patterns with explicit undo functions. Inngest offers step-level error handling that can trigger cleanup steps. Each relies on developers to codify compensation; none automatically reverse external side effects, so compensating logic must be carefully tested per integration and often requires idempotency safeguards.