What is the Loopback Detected Message in my Mission Log?

Don't be alarmed, this is just a detection by the agent that a block has either a connection looping from it's output back to it's input or it has one or more of it's outputs that has no connection.

The reason for this message is to let the user know that a delay is automatically being inserted into the connection or in the case of a no connection, it is waiting in a delay and reevaluating to see if another connection result might be connected.

All task blocks will use a loopback delay of 1 hour. If you don't want a full hour for your reevaluating of the block see below on how to bypass the loopback delay.

Example of a Block Loopback

Here is a commonly used scenario where a FALSE output is connected back to the input of the same block. This is totally acceptable.

Bypassing Block Loopback Delay

If you don't like the default value of this delay, or the Loopback Detect message in your mission log you can simply insert a delay block into the loopback. In the example below the loopback delay is bypassed by adding in a delay block. Now the block will be reevaluated every second.

Another Reason for Message

Sometimes you might forget to connect an output of a block and when the block triggers that unconnected output you will get a loopback detect warning. It will wait the standard loopback delay and will try to evaulate the block again. It will continue doing this until a valid output is triggered or the output is fixed and the agent mission is relaunched.