Is Agent Active

This task block will check to see if an agent running a mission is active.

This task block consists of an input and two outputs Active and Not Active .

If the input to the block is triggered the block will lookup the status of the agent using the Agent ID stored in a variable.

Examples

Here is a simple example that launches an agent with a mission and then checks if the agent is active. If the agent is active then a message is logged to the mission log. If not active a loopback check will be thrown and the Is Active Agent block will be checked in another hour.

Copy / Settings / Docs

Each task block has three buttons named Copy, Settings, and Help.

• Copy: This will duplicate the task block with all the current settings.
• Settings: Settings will show a dialog that allows some added configuration for the block
  • Note: This allows you to add a text note for the current block. This note will appear in the log file if the Block Loggin option is enabled.
  • Transition Out Time: Each block can specify a delay in milliseconds that it will wait after an output trigger is activated. This feature is generally not used but is avilable for more granular flow control of the mission if needed.
  • Block Logging: If this is enabled then the internal logging of the block is turned on and will be sent to the mission log. Each block has different amounts of internal logging which can make mission logs become large in some cases. Users generally do not enable this feature because of the limits to data storage.