Neurons Bots Results

The Neurons Bots results page displays when you:

To edit the bot name click pencil icon, the Rename dialog appears.

Description: To view or edit the bot/survey description select Description, the Bot/Survey description panel appears. Select Save to save any changes.

Survey results: This button only displays for survey bots. Select to display the Survey Results page.

Versions

All versions of the bot are listed under the Versions drop-down. Select a version to display the results in the work area. The latest version is always the current version. Learn more about Neurons Bots versioning.

Filters

  • Version: Select the version of the bot you want to view the results for.
  • Time: Select a time range to filter the result data. The default is Last 7 Days. The maximum is limited to the last 90 days.
  • Triggers: Select the source trigger to filter the result data; Schedule triggers, Custom Action triggers, Run Now, or All triggers. The default is All triggers.
  • States: Select the last run device state to filter the result data; All states, shows all runs for all devices. Last state only, shows the last generated run per unique device including if the last run is still in progress. The default is All states.

Actions

Select a version of the bot, and select Edit version to edit the bot stages or settings. When you have made all changes select Save and publish this creates a new version of the bot. Learn more about Neurons Bots versioning.

Select to start a bot run immediately:

  1. Click Run Now. The Run now dialog displays.
  2. In the Run now dialog, select a Target group to run the bot against.
    Target groups are set up in Ivanti Neurons > Devices > Groups. The device group must be a Public Group.
  3. Select the Target scope. The scope is a percentage, in 10 unit intervals, between 10% to 100%. The scope randomly selects a number of devices within the target group, it does not detect whether the devices are online or offline.
    Note: A minimum of one device will always be selected, regardless of the percentage threshold.
  4. Select the Device run behavior. There are two options to choose from:
    • Run for online devices - Choose this option to run the custom actions only on devices that are currently online.
    • Run for online devices and queue offline devices to run when next online - Choose this option to run the custom actions immediately on online devices. For offline devices, the tasks are queued and will run when they come online.
  5. Specify the Days to wait before timeout. Enter the number of days to wait for the device to come online. If the device does not come online within the specified time period, the run request times out. The Maximum waiting period is 28 days.
  6. If the bot has any Bot inputs, you must set the mandatory ones.
    Bot inputs are setup on the Bot editor page. Learn mo re about Bot inputs.
  7. Click Run now. The trigger in progress dialog displays.
  8. The Trigger history and Device history will update as the Bot progresses.
    The successful or failed trigger details can be viewed in the Trigger history.

Select to view version details for a bot:

  1. Select the Version of the bot you want to see more information on. The Version information panel displays.
    The information displayed depends on the trigger type and status:
    • Version: The bot version number.
    • Trigger type: The bot trigger type: Schedule or Custom action.
    • Trigger status: The status of the bot;
      • active/inactive - for current version.
      • was active/was inactive - for past version.
    • Target groups: The target device groups on which the bot will run. Only applicable for active scheduled bots.
    • Frequency: The schedule frequency the bot is due to run on the target groups. Only applicable for active scheduled bots.
    • Custom action display name: The bot name as it will display in the Device Action panel. Only applicable for active custom actions.
    • Created: The date and time the version of the bot was created.
    • Created by: The name of the person that created the version of the bot.
    • Version comments: Any descriptive text relating to the bot version creation.

You can terminate a running bot at any stage to stop further processing. This ensures better control, efficiency, and flexibility in bot management. This functionality helps to deal with unintended executions, stop faulty workflows, and prevent unnecessary actions that could cause errors or performance issues.

To cancel a running bot:

  1. On the Neurons Bots homepage, select Trigger history.
    The Trigger history page appears.
  2. In the cancel column, select Cancel in the in-progress bot to terminate the bot
  3. Select OK to confirm the cancellation.

Or

  1. On the Neurons Bots homepage, select the name of the bot you want to cancel.
    The Neurons Bots results page appears.
  2. In the Trigger history section, select Cancel running to stop all targets of a bot in a particular version.
    Or select View details to stop individual targets.
    The Trigger history page appears.
  3. In the cancel column, select Cancel in the in-progress bot to terminate the bot.
  4. Select OK to confirm the cancellation.

Results view

The Results view displays the Trigger and Device history, and the bot stages together with their run results.

Trigger history

The Trigger history section indicates the number of times the bot had been triggered. The following trigger states are recorded:

  • Attempted: The number of times the bot version has been triggered, either by a Schedule, Custom Action, or as a manual run now action.
  • Failed: The number of times a trigger has failed, such as a system error has occurred, or the target devices for the bot cannot be found.
  • Fired: The number of times the trigger has been successful.

Click View details to display the Trigger History page.

Device history

The Device history section indicates the number of devices targeted by the bot. The following device states are recorded:

  • In scope: number of devices in the selected Devices target group.
  • Unavailable: number of devices that are offline in the Devices target group.
  • Targeted: number of devices that are online in the Devices target group which the bot will run against.

  • Successful: number of devices where the bot has successfully completed all stages.

  • With error: number of devices where the bot has a failed or timed-out stage. It depends on the configuration whether the bot continues to run for the devices without error.
  • In progress: number of devices where the bot is still running.

Stage results

All the stages of the bot display in the results area. The trigger stage displays the status Active/Inactive, and for a Custom action trigger the number of users that the bot is visible to is also shown. Hover over the number to display the names of the users who have been granted access to view and run the bot as a Custom action in Devices.

All other stages contain run metrics, the metrics shown are restricted by the results filter criteria and depend on the type of stage:

Stage type: Queries and Filters

  • Performed : the number in the top right of the Stage indicates the number of devices on which the Query/Filter was performed during this bot version.
  • Run in progress icon In progress: number of devices the Query/Filter is currently still in progress for this bot version.
  • Run failed icon Failed : number of devices the Query/Filter has failed on for this bot version.
  • Run successful icon Matched : number of devices where the Query/Filter criteria has been successful for this bot version.

    • A Query/Filter is successful even if there are no results. For more detail see the stage tooltip which shows Queries matched and Queries not matched.

Stage type: Actions and Interactions

  • Performed : the number in the top right of the Stage indicates the number of devices the Action/Interaction was performed on during this bot version.
  • run in progress icon In progress: number of devices the Action/Interaction is currently still in progress for this bot version.
  • run failed icon Failed: number of devices where the Action/Interaction has failed for this bot version.
  • run successful icon Successful: number of devices where the Action/Interaction has been successful for this bot version.

Click any of the stage metrics, that has a number greater than zero, to display the Stage results details page.

Stage results details

The Stage results details page displays when you select a stage metric. The details table will be dependent on the type of stage. If the stage is connected to another application, a link is available to click and go to a deeper level of detail. For example, the Create or update ITSM Ticket stage has an Open in ITSM link, this opens the corresponding ticket in Ivanti Neurons for ITSM.

Related topics

Trigger History

Neurons Bots versioning

Neurons Bots editor