Reason for not Acquiring a Resource

Question

question

Sebastian Hemmann asked Feb 01 2018 at 10:09 PM Pinakin K commented Nov 14 2018 at 3:17 PM

Reason for not Acquiring a Resource

Hi,

does anybody have a clue what could be a reason for a token to not taking a Resource if there is all available?

In the Picture you see the resource. It has a link to a Group that has 6 members. But on any Point in my model (Client sensitive) it stops getting the sixth resource.

I tryed a lot but can´t find out what could be a reason for that?!

Software Version:

FlexSim 18.0.2

process flow resources acquire

resource-problem.jpg (21.1 KiB)

· 3

Mischa Spelt commented · Feb 02 2018 at 4:59 PM

May a resource is not released properly. Do you have any tokens sitting in a Sink or Finish activity that normally should have been cleaned up yet? Do you acquire specific resources using queries, where it is possible that at some point the sixth resource just stops matching your query conditions?

0 ·

Sebastian Hemmann Mischa Spelt commented · Feb 03 2018 at 10:11 AM

Hi Mischa,

sorry for not saying what I already tryed out. No there are no Tokens waiting in any Sink or Finish activitys. Also I had a look into all Acquire and the Resource Activity itselfe. No Queries that could stop a token to match to the resource.

I further had a look into the Label the resource is stored in before releasing, there is no Array or anything else. And I tryed ot the "Release All" Pickoption.

0 ·

Matthew Gillespie ♦♦ commented · Feb 02 2018 at 5:54 PM

Can you post the model, or make a sample model that shows the issue?

0 ·

______

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 · 2018-02-03T14:15:12Z

Sebastian Hemmann answered Feb 03 2018 at 2:15 PM Pinakin K commented Nov 14 2018 at 3:17 PM

Ok, Support (Matthew Gillespie) figured out that:

Because I use Split and Join Activitys the Token that pulled the resource is destroyed in a Join Activity. This happens because I didn´t have a look in what order I connected the Join Activity. This Activity destroys all Tokens except the one arriving via Connector 1.

So switching the order of connections solved my Problem.

· 1

question