Bot States & Lifecycle Actions

Bots have several states and lifecycle actions that are available to end-users. Please take a look at the information below.

States

Bot states are controlled via the action menu. Simply select one or more listed bots to transition them to the desired state.

  • Running: The bot is operational and functioning on select hookpoints and/or schedule.
  • Paused: The bot is in a suspended state and is not taking action. This state is typically found on newly created bots and/or bots that are in development.
  • Archived: The bot is no longer in use, but is kept around for historical/auditing purposes.
  • Scanning: The bot is currently performing a retroactive scan of the configured scope.

Lifecycle Actions

The following lifecycle actions are available:

  • Resume: Transitions a paused/suspended bot to a running state. Any hookpoints and schedules configured will be used as the bot’s execution point.
  • Pause: Suspends a running bot. Typically this is done on newly created bots or bots that you want to suspend for maintenance.
  • Archive: Permanently disables a bot. The bot’s history and metadata is retained, but scheduled events and noncompliance data is purged.
  • Update: Allows you to make changes to information about the bot, e.g., its name, description, or category, etc. without affecting the bot’s state.
  • Reconfigure: Allows you to make changes to bot properties, e.g., its filters/actions, schedule, and hookpoints. Importantly, if you Reconfigure a bot, it will change to Paused state. You will need to Resume the bot to change its state to Running. Reconfigure will not allow you to change bot scope. If you want to change bot scope, Copy the bot and apply the new scope to the new bot.
  • Save as Template: Allows you to create a bot template from which to create bots more simply and consistently.
  • Copy: Copies the configuration of one bot to another. This action is useful when only changes to bot scope are needed.
  • Ondemand Scan: Runs a scan against all known resources within the configured scope. Typically this action is useful when you want to retroactively audit/enforce policy.