Outstanding Actions
Actions affect either TIBCO host or nodes, so the TIBCO host and node must be running to execute the actions. For example, if a machine is down, actions targeted to objects running on that machine will fail. However, Administrator supports an offline mode for many actions. This means that actions in Administrator are queued up while runtime objects are offline and executed when they comes back online.
While a target runtime object is offline (either not running or unreachable) queued actions in Administrator wait their turn for execution. For example, if a host is offline, actions performed against the host will remain queued, and will execute as soon as the host comes back online.
An application distributed to several runtime nodes may be deployed while some nodes are online and some are offline. Administrator will split the deployment action into multiple tasks, some of which are executed right away and others put on a queue for future execution when their target node comes online.
An action is complete when all its tasks, including those placed on the queue, are done executing. For the offline case, an action may take a very long time to complete. Even in the online case, certain asynchronous actions may take a long time to complete.