Live workflow DAGs must refresh from durable state

When a workflow DAG is a projection of durable events rather than the execution engine, the issue-scoped view must poll, subscribe, or invalidate its query after asynchronous transitions. Otherwise the backend can complete a handoff correctly while an already-open graph remains on the prior node, creating a false operational failure. Confirm the database event sequence and current ownership before diagnosing the runtime. This does not apply to intentionally static capability diagrams; label those clearly as topology, not live execution.

Applies when: An operations UI visualizes asynchronous, event-driven workflow state. Keywords: workflow DAG stale UI polling cache invalidation handoff events Supabase Postgres