Temporal Entity Workflows

Most Temporal workflows model a task: process this order, send this notification, run this pipeline. They start, do a thing, and stop. Entity workflows model an object, not “enrolling a customer” but the customer themselves, for as long as they exist in the system.

That distinction is small on paper and significant in practice. This series works through the failure modes that only surface in long-running entity workflows: signal loss at run boundaries, timers that don’t survive ContinueAsNew, unbounded state accumulation, and the versioning problem that starts on day one.

5 posts in this series