Creating one or more contexts makes the correlator non-deterministic. In other words, injecting the same monitor can product different results if the monitor contains statements that spawn to contexts.

For example, suppose an application creates two contexts, spawns to each of them, and each context runs code that calls integer.getUnique(). The assignment of unique integers to contexts is not deterministic; if you re-run the code, each context might receive an integer that is different from the integer it received during the previous run. Other behavior that can be non-deterministic in a parallel processing application includes the following:

See also About input logs and parallel processing in Deploying and Managing Apama Applications.