question

Clair A avatar image
0 Likes"
Clair A asked Jonah K edited

Tagged resource: invalid down cast

In the Tagged Resource pickoption, the Team parameter can be used to reference a dispatcher:

1689927475608.png

However this throws an exception:

FlexScript exception: Invalid down cast. Object is not an instance of the target type. at MODEL:/Queue1>variables/transportdispatcher

See attached example: Tagged resource invalid down cast.fsm.

Under the hood, the code uses the TaskExecuter class, but the dispatcher is not an instance of that class.

Could you please fix that bug ?

FlexSim 23.0.9
tagged resource
1689927475608.png (11.2 KiB)
tagged-resource-invalid-down-cast.fsm (35.8 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Julie Weller avatar image
0 Likes"
Julie Weller answered Jonah K edited

I've been able to duplicate it in every version of Flexsim I've tried! I'll send it to dev as a bug

· 5
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jonah K avatar image Jonah K ♦ commented ·

@Clair A This has been fixed in FlexSim 23.0.15 released today.

1 Like 1 ·
Clair A avatar image Clair A commented ·
Thanks @Julie Weller. My colleague @Allister Wilson already reported the same bug by email to [email protected] in May 2021. @Jordan Johnson could you please increase the priority of fixing this bug ?
0 Likes 0 ·
Jordan Johnson avatar image Jordan Johnson ♦♦ Clair A commented ·

Will do!

0 Likes 0 ·
Clair A avatar image Clair A Jordan Johnson ♦♦ commented ·
@Jordan Johnson when is this bug going to be fixed ?

Once again a user reported to me yesterday that he tried to use the Tagged Resource pickoption but it still throws the same exception as reported by Allister in May 2021 to [email protected], and as reported once again in the post above in July 2023.

I tried in 24.0.2 and even in 24.1.0 beta released yesterday, it still throws the same exception.

0 Likes 0 ·
Show more comments