Legacy Dev Forum Posts

 View Only

Sign Up

Architect Action API Isn't Pulling In New Common Module Version

  • 1.  Architect Action API Isn't Pulling In New Common Module Version

    Posted 06-05-2025 18:24

    Cory_King | 2022-11-16 17:40:14 UTC | #1

    Hello - We are working on a feature to check out/check in/publish a flow so we can automate pulling in the most recent published version of a common module into a flow. Here is our use case: We have Flow A that references Common Module Version 1 We edit Common Module Version 1 creating Common Module Version 2 We want to check out/check in/publish the call flow over API and have the call flow reference Common Module Version 2. I've been playing around with the following APIs and calling them in this order: /api/v2/flows/actions/checkout /api/v2/flows/actions/checkin /api/v2/flows/actions/publish

    When i follow this pattern, the published flow will still reference Common Module Version 1

    Is there a way I can accomplish my goal of having the flow pick up the new Common Module by publishing over API?

    Thank you, Cory King


    Cory_King | 2022-11-16 18:49:14 UTC | #2

    I also reached out on the Community forum and was directed to use Archy. I'm going to pursue that route.


    system | 2022-12-17 18:50:08 UTC | #3

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 17250