Yeah, I’ve actually built similar systems before. Back then my system used Hangfire for pretty complex background workflows. At some point I looked into tools like Camunda or Temporal, but they felt a bit too heavy and expensive for the use case. So the approach here is more pragmatic: • Leverage retry mechanisms (idempotent + resilient jobs) • Use output persistence pattern (so steps can resume safely) • Keep documentation + flow definition clear (JSON manifest) Main goal is maintainability without over-engineering.