This is event function takes a text attribute that specifies the name for a configuration that is to be installed at this time. If no configuration of that name exists, then nothing happens as a result of this call, and the simulation continues in the same state that it was already in. Users of configuration management under run-time control have a number of opportunities to put their simulations into unstable states or tight loops. We suggest that frequent saves with different file names be practiced by simulation authors who are using the feature. In addition Be careful not to generate a large number of configurations under rule control.
Configurations take a great deal of memory, because they capture everything about a simulation.
The larger the simulation, the more memory they take up. Use the DeleteConfiguration feature to get rid of unneeded configurations.