jimiFlows primarily execute and run an active jimi_core instance, however some actions have the option to use the remote plugin to execute certain actions on alternative systems. This can be very useful for remote scanning using nmap and/or openVas as you may not want the jimi_core instance to be exposed to untrusted networks.

If your using an object and it has a ticket box "runRemote" then ensure you have a remote connect object before and when ticket it will run on the connected system.

Not everything in jimi can work like this as many of the actions and triggers require access to the mongo database - possible future issue is already logged to look at how these could be proxied through jimi_core so that entire sections of flows could one day be run on different remote systems. - This is not likely to be in place until at least version 3.0