Run sibling tokens through same process flow

Question

question

Ben Wychocki asked Mar 26 2025 at 6:07 PM Felix Möhlmann answered Mar 27 2025 at 7:52 AM

Run sibling tokens through same process flow

I have a system where I want a token to split into a number of sibling tokens. Each token goes through a different Set Labels activity, then they are all run through the same process flow. Multiple original tokens would be in this process flow at the same time. What is the best way to have the siblings be rejoined at the end? The regular Join activity requires multiple inputs, and I can't find a good way to send siblings from the same parent token down different paths to the join activity.

Ideally I would just have a single path into a Join function and the sibling tokens would wait until all siblings from one parent are present, then the parent leaves. What is the best way to replicate this behavior?

Software Version:

FlexSim 25.0.2

process flow sibling token

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2025-03-27T07:52:20Z

Felix Möhlmann answered Mar 27 2025 at 7:52 AM

It sounds more like you are creating child tokens, but that doesn't really matter. (Sibling Tokens are defined by having the same parent. Creating a sibling from a token with no parent is not possible, the resulting token would be independent).

You could use a Batch activity and group the tokens by the splitID (if you used a Split activity to create the tokens). There isn't a way of making sure that only the parent gets released though. So I would simply release all tokens and sort out the child tokens by sending them to a sink in Decide activity afterwards.

question