> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/how-to/run-workflows-manually.md).

# Run Workflows Manually

Run a Lifecycle Management workflow outside the extraction cycle, for one identity or for many identities at once

## Overview

Lifecycle Management runs a policy's workflows during the normal extraction cycle. To run a workflow outside that cycle, use **Run Workflow Manually**. For example, re-run a joiner workflow for a new hire, or apply a new workflow to identities that already exist.

You can run a workflow manually in two ways:

* For one identity: from the identity's ⋮ menu on the **Identities** page
* For multiple identities: from the workflow's card on the policy's published version

The two entry points have different availability rules. See [When the option is unavailable](#when-the-option-is-unavailable).

{% hint style="warning" %}
A manual run executes the workflow's actions against live systems, and Veza does not roll back the changes. To preview the results without making changes, run a [dry run](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/how-to/test-policies-with-dry-run.md) first.
{% endhint %}

A manual run also runs a workflow that is [disabled](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/how-to/disable-workflows-and-actions.md) in the policy, once, for the identities you select.

## Before you start

* Running a workflow manually requires the Administrator role. See [Roles](/4yItIzMvkpAvMVFAamTf/administration/administration/users/roles.md).
* The policy's published version must contain at least one workflow.

## Run a workflow for one identity

1. Go to **Lifecycle Management** > **Identities**.
2. Open the ⋮ menu for the identity, on its row or in its details view.
3. Select **Run Workflow Manually**.
4. In the **Manually trigger workflow for** *identity* dialog, select a workflow from the **Workflow** list.
5. Select **Run Workflow**.

When the run is queued, a message confirms that the workflow was triggered for the identity. If the selected workflow has no actions, a warning states that the workflow has no actions, and nothing runs.

To follow the run, open the **Workflow Tasks** tab of the [Provisioning Activity](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/getting-started/activity-log.md) page. The **Manually Triggered** column shows **Yes** for manual runs.

## Run a workflow for multiple identities

Run a workflow for every identity in a policy, for identities you select, or for identities that match a filter.

1. Go to **Lifecycle Management** > **Policies** and open the policy.
2. In the **Policy Versions** panel, open the published version's [version page](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/policy-and-version-pages.md#version-page).
3. Select the **Workflows** tab.
4. On the workflow's card, open the ⋮ menu and select **Run Workflow Manually**.
5. In the **Run workflow manually** dialog, under **Select Identities**, choose one option:
   * **Select All**: run the workflow for every identity in the policy.
   * **Select Identities individually**: select up to 100 identities from a list of active identities. If you select more than 100, the dialog shows **Select at most 100 identities** and **Run Workflow** is unavailable.
   * **Select Identities based on properties**: enter a SCIM filter on identity attributes. Select **Show matching identities** to open the matches in a new tab. After you enter a filter, the button shows how many identities match, up to **More than 1,000 matching identities**.
6. Optionally, select **Only run identities currently matching this workflow's condition**.
7. Select **Run Workflow**.

The filter uses the same syntax as workflow trigger conditions. See the [Trigger conditions reference](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions/trigger-conditions-reference.md). **Select Identities based on properties** is unavailable when the policy has no data source attributes.

**Only run identities currently matching this workflow's condition** is cleared by default, so the workflow runs for every selected identity. With it selected, Veza skips any selected identity that does not currently match the workflow's trigger condition.

A confirmation message states that tasks are being created for the selected identities. Select **View Workflow Tasks** to open the **Workflow Tasks** tab of the [Provisioning Activity](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/getting-started/activity-log.md) page, filtered to this run. For **Select All** and filter runs, tasks are created in the background, so the tab fills in as the run progresses.

## When the option is unavailable

On the **Identities** page, **Run Workflow Manually** appears only when the policy is running. A paused or initial policy does not qualify.

On a workflow card, **Run Workflow Manually** is unavailable when the workflow cannot be run manually, and a tooltip gives the reason:

| Reason shown                                                        | What to do                                                                                                                                                                                                                                                                 |
| ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Publish a policy version to run a workflow manually**             | The policy has no published version yet. Publish a version, then run the workflow from it.                                                                                                                                                                                 |
| **Only workflows in the published version can be run manually**     | You are viewing a draft or a retired version. Open the published version instead.                                                                                                                                                                                          |
| **The policy must be enabled or paused to run a workflow manually** | On the **Policies** page, open the policy's ⋮ menu, select **Enable**, and confirm. See [Policy state versus workflow versioning state](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/policies.md#policy-state-versus-workflow-versioning-state). |

## See also

* [Identities](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/identities-overview/identities.md)
* [Policy page and version page](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/policy-and-version-pages.md)
* [Policies](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/policies.md)
* [Test policies with dry run](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/how-to/test-policies-with-dry-run.md)
* [Disable workflows and actions](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/how-to/disable-workflows-and-actions.md)
* [Provisioning Activity](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/getting-started/activity-log.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/how-to/run-workflows-manually.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.