All features supporting the SysML v2 BETA specification are currently ALPHA and subject to change. The final SysML 2.0.0 specification is expected to be officially adopted in the second half of 2025. While there have been many questions during the finalization, we believe this implementation provides enough value for early adopters to start preparing to create and execute models using the new specification. We will be expanding support for the specification through finalization, into SysML v2.1, and beyond. There are a small number of remaining issues related to execution scheduled for revision in SysMLv2.1. We will be expanding and clarifying support for SysML v2.x throughout the upcoming language revision process. Consult the What's New and Modeling with SysML v2 pages for more information about what is currently supported.

Troubleshooting

Running Simulations

If you see unexpected simulation log output, and need to see if/when the Behavior Execution Engine executed a specific performance from your model, finding the element id in the System Architecture Modeler and searching the execution log for it helps to gather information about the problem.

If you have Objects in your model with performances that do not appear in a simulation trace contrary to expectation, ensure that the Object has an explicit non-zero multiplicity defined. Objects that have multiplicity lower-bound of zero will not be executed during simulation. The multiplicity lower bound of the Object may default to zero if not explicitly defined otherwise.


If you have defined a transition with a trigger action that the Behavior Execution Engine appears to ignore, ensure that the transition is a State Transition and not a Non-State Transition. This is because Behavior Execution Engine ignores any trigger action defined on Non-State Transitions. The Behavior Execution Engine considers transitions that have a State source as State Transitions, and transitions with other source types (e.g. Action) as Non-State Transitions.


If you have created a delegate implementation of an action, Behavior Execution Engine will not execute any subActions defined in the model. Delegation acts as an override of the modeled action, meaning none of the modeled information that is owned by the action will be used during simulation.