I had seen some previous work about actions allocated to parts in swimlanes and how Cameo keeps track of whether or not the runtime instance attached to the part is "busy" before execution. This effectively limits each object to doing at most one activity at a time. I rediscovered this after a few hours of debugging where I had the object at the top of a swimlane with an activity with streaming pins and other actions happening. The action with streaming effectively blocked all other activities from happening. When I killed the streaming activity (used the Stop button on that activity), everything else proceeded as expected.
Is there a setting to turn off this blocking expectation? I don't know if it matches the specification that a given active object can perform exactly one behavior at once.
