Common module versioning — published changes not reflecting in parent flow

I updated a common module, published it, but the parent flows still use the old version.

The parent flow calls CommonModule_v2 which I updated with a new Data Action. But live calls still execute the old logic. Do I need to republish every parent flow that references the module?

Yes. Parent flows cache the common module version at PUBLISH time.

When you publish a parent flow, it snapshots the current version of every referenced common module. If you update the module later, the parent flow still uses the old snapshot. You must republish every parent flow to pick up the module changes.

We manage 50+ flows and this republishing requirement is our biggest operational pain point.

Every module update requires republishing 12 parent flows. We built a Terraform pipeline that detects module changes and automatically republishes all dependent parent flows. Without this automation, module updates would take 2 hours of manual clicking.