---
title: Trigger App Distribution
slug: neurons/help/en_us/trigger-app-distribution
createdAt: 2026-11-05T08:02:06.718Z
---

The **Trigger App Distribution** stage can be used in a bot to utilize the **Distribution** feature in Ivanti Neurons Platform. Using this stage within a bot allows the selected application or bundle to be distributed for installation to devices either on a schedule or as a custom action, based on the other stages in the bot workflow. For example, admins can use bot-initiated chat to allow the end user to decide when and if the software install takes place, so it is convenient for them and their work schedule.

The **Trigger App Distribution** stage provides package details for the selected item from the **Application Catalog**. This helps to differentiate between an application and a bundle using the **Package type** catalog field to avoid confusion during deployment, especially when a package is mislabeled. It also offers failure analysis if the bot’s action fails; the results panel displays which packages succeeded or failed. You can expand entries to see detailed failure reasons, which is particularly useful when dealing with bundles containing multiple applications.

:::hint{type="info"}
Detailed information is not stored permanently; it is always retrieved live from the distribution system. As a result, the latest status may differ from any previously stored summary.
:::

The Distribution feature is available with the Ivanti Neurons for Healing license. Learn more about [Distribution](docId\:hQNOUpGvz3lgPKlg7gnSq).

## Prerequisites

There are some prerequisites before you can add the stage to a bot:

- You must have first added applications to the **Catalog** in Distribution. The applications must have been made available for on-demand install.
- The Agent Policy on the target device that the bot is to run on, must have the **App Distribution** capability enabled. Learn more about [Agent Policy Capabilities](docId\:vpvQGvcgc3zSgU1IjLAIL).

## Stage timeout

The default setting for the period that the bot will await a response from the Distribution service is 25 minutes. The time denomination and the number is configurable in the bot **Stage settings**.
If this period is exceeded the bot will report a fail. The Distribution itself will remain queued against the device, this can be managed from within Distribution.
