Processor “On State Change” trigger only allows “Do Nothing” – no actions available

Processor “On State Change” trigger only allows “Do Nothing” – no actions available

dengels1805
Community Visitor Community Visitor
236 Views
1 Reply
Message 1 of 2

Processor “On State Change” trigger only allows “Do Nothing” – no actions available

dengels1805
Community Visitor
Community Visitor

Hi everyone,

I am running into a limitation (or bug?) in FlexSim related to triggers on Processor objects and I would appreciate some clarification.

My setup

  • Two Processor objects in sequence (P1 → Buffer → P2).

  • P2 has a defined setup time.

  • No operators, no Process Flow, and no custom code (FlexScript) – only standard object logic and triggers.

  • Goal:
    When P2 starts its setup, P1 should pause, and once the setup is finished, P1 should resume.

The core problem

On Processor 2, I tried to use the “On State Change” trigger to detect when the processor enters the Setup state.

However, in the trigger configuration:

  • The only selectable action is “Do Nothing”

  • No object actions are available (e.g. Stop Object, Resume Object, Close Input, Send Message, etc.)

So even though “On State Change” exists as a trigger option, it is effectively read-only and cannot be used to control other objects.

Does anyone know, how i can proceed with this problem, without using operators or FlexScript. 

Thank you guys

0 Likes
237 Views
1 Reply
Reply (1)
Message 2 of 2

FelixMoehlmann
Collaborator
Collaborator

Option 1: Add and configure the trigger functions you want in a different trigger and then just copy over the code to the state change trigger. You need to make sure that you don't use parameters that are not present in the state change trigger (for example "item" would not be defined). But as long as you only use "current" this should work.

Option 2: Use Process Flow. Listen to the event with an Event-Triggered Source and use the pickoptions of the "Custom Code" activity (opening/closing, stopping/resuming would be under "Control").

 

I can imagine that the state change trigger has no options because it's quite easy to create an infinite loop by doing something in the trigger that would update the state (like stopping the object).

0 Likes