The route command generates a new event that goes to the front of the input queue of the current context. Any active listeners seeking that event then receive it. There is only one difference between an externally sourced event (passed in through a live message feed) and an event that was generated internally through a route command. The difference is that internally routed events are placed at the front of the context’s input queue in the same order as they are routed within an action, and after any previously internally routed events where multiple listener actions have been triggered by an event. The correlator processes the routed events on the input queue before it processes the next non-routed event on the input queue. See Event processing order.

For example:

The simulateCrash() action shown above routes six StockTick events for the monitor’s specific stock name, with drastically reducing prices. Other monitors (or the same monitor) may receive these events and process them accordingly.

You cannot route the following types:

Note that you can route an event whose type is defined in a monitor.