> 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/getting-started/activity-log.md).

# Provisioning Activity

Understanding the Lifecycle Management Provisioning Activity page for tracking provisioning operations

The **Provisioning Activity** page provides visibility into all provisioning operations performed by Veza's Lifecycle Management system. It serves as a record of all activities, including successful actions, errors, and failures.

### Overview

A Lifecycle Management policy defines automated workflows that execute when changes occur in a source of identity. The Provisioning Activity page tracks all aspects of these operations through a hierarchical structure:

1. **Policies** define the overall automation framework for managing identities
2. **Workflows** determine which actions should be executed for specific identities
3. **Actions** represent specific operations to be performed on target systems
4. **Jobs** are individual tasks executed as part of actions
5. **Events** record atomic changes resulting from successful jobs

The Provisioning Activity page provides four views of this activity across different tabs: **Workflow Tasks**, **Workflow Actions**, **Integration Jobs**, and **Events**.

#### Workflow Tasks stats card

When the page opens, a **Workflow Tasks** stats card shows live totals of **Scheduled**, **Waiting**, and **Running** tasks, followed by **Done** and **Errored** counts under **Last 24 Hrs**. Use this card to get an at-a-glance health check without applying any filters. Scheduled and Waiting counts show how much work is pending, and Running shows what is actively executing.

### Provisioning Activity tabs

Each tab can help track recent actions, verify that expected changes have occurred, identify patterns or issues in lifecycle events, and monitor the overall health of your Lifecycle Management implementation.

#### Events Tab

The Events tab shows individual changes made to entities and relationships within the system. Each event represents an atomic change resulting from a successful action.

| Column             | Description                                                                                     |
| ------------------ | ----------------------------------------------------------------------------------------------- |
| Event Type         | The type of event that occurred (e.g., REMOVE\_RELATIONSHIP, ADD\_RELATIONSHIP, SYNC\_IDENTITY) |
| Timestamp          | When the event occurred                                                                         |
| Success            | Whether the event completed successfully (True/False)                                           |
| Identity           | The identity associated with the event                                                          |
| Local User         | The account affected by the event (hidden by default)                                           |
| Entitlement Entity | The entitlement entity involved, if applicable                                                  |

#### Integration Jobs Tab

The Integration Jobs tab displays individual jobs executed as part of actions. Jobs represent specific tasks performed on target systems, such as creating a user account or updating attributes. Use this tab to review whether individual jobs executed successfully or encountered an error and could not be completed.

| Column       | Description                                                              |
| ------------ | ------------------------------------------------------------------------ |
| Parent       | The name of the action or access request that initiated the job          |
| Parent Type  | Whether the job came from a **Workflow Action** or an **Access Request** |
| Integration  | The target integration                                                   |
| Job Type     | The type of action (e.g., Sync Identities, Manage Relationships)         |
| Workflow     | The workflow that ran the action, if applicable                          |
| Started At   | When the job started                                                     |
| Completed At | When the job completed                                                   |
| Duration     | How long the job ran                                                     |
| Identity     | The identity associated with the job                                     |
| State        | The current state of the job (Completed, Errored)                        |
| Any Changes  | Whether the job resulted in changes to the system                        |
| Policy       | The policy that ran the job (hidden by default)                          |

[Rotate Key](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions/rotate-key.md) runs started from **NHI Security** also appear on this tab and the Events tab. They have no associated identity, so only users with the **Administrator** or **Operator** role can see them.

#### Workflow Actions Tab

The Workflow Actions tab shows high-level operations triggered by workflows. Actions typically involve one or more jobs that work together to accomplish a specific goal.

| Column       | Description                                                      |
| ------------ | ---------------------------------------------------------------- |
| Name         | The name of the action                                           |
| Action Type  | The type of action (e.g., Sync Identities, Manage Relationships) |
| Workflow     | The workflow that ran the action                                 |
| Identity     | The identity associated with the action                          |
| Started At   | When the action started                                          |
| Completed At | When the action completed                                        |
| Duration     | How long the action ran                                          |
| State        | The current state of the action (Completed, Errored)             |
| Jobs Started | Number of jobs initiated by this action                          |
| Any Changes  | Whether the action resulted in changes to the system             |
| Policy       | The policy that ran the action (hidden by default)               |

See [Actions](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions.md) for more details on supported actions and configuration options.

#### Workflow Tasks Tab

The Workflow Tasks tab displays workflows executed for specific identities. Workflows represent a sequence of actions executed as part of a Lifecycle Management [Policy](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/policies.md).

| Column             | Description                                                                                         |
| ------------------ | --------------------------------------------------------------------------------------------------- |
| Name               | The name of the workflow                                                                            |
| Identity           | The identity for which the workflow was executed                                                    |
| Entity Type        | The type of entity processed by the workflow (hidden by default)                                    |
| Created At         | When the workflow task was created (hidden by default)                                              |
| Scheduled For      | When the workflow was scheduled to run, if applicable                                               |
| Started At         | When the workflow started                                                                           |
| Completed At       | When the workflow completed                                                                         |
| Duration           | How long the workflow ran                                                                           |
| State              | The current state of the workflow (Completed, Errored)                                              |
| Policy             | The policy the workflow belongs to (hidden by default)                                              |
| Manually Triggered | Whether the workflow was triggered manually (**Yes**) or by an automatic policy evaluation (**No**) |

### Workflow Execution Process

For each identity, Lifecycle Management follows this process:

1. **Validation**: The system validates the identity against workflow trigger conditions
2. **Execution Determination**: The system determines whether execution is needed based on:
   * Identity state (e.g., CREATED, CHANGED, UNCHANGED)
   * Continuous sync settings
   * Last execution time (for unchanged identities)
3. **Task Creation**: If execution is needed, a workflow task is created
4. **Action Execution**: The system executes conditions and actions via the task runner
5. **Result Storage**: The result is stored as an event on the Provisioning Activity page

### Using the Provisioning Activity page

The Provisioning Activity page provides filtering and search options to help locate particular events:

* **Filter by recent extraction**: Use the **Recent Extractions** filter to select one of the five most recent extraction events (shown with provider logo, relative timestamp, and policy name). Selecting an extraction scopes the Workflow Tasks table to that run in a single click, without manually entering a time range.
* **Filter by time period**: Use the date range filters to focus on a date range
* **Search by identity or entity**: Use the search fields to find activities related to unique identities or entities
* **Filter by event type or state**: Use the dropdown filters to focus on event type or state
* **Filter by manually triggered**: In the Workflow Tasks tab, filter to show only manually triggered workflows or only automatically triggered ones
* **View error messages**: Click the link in a row's first column to open its details panel, which shows the full error message

### Common tasks

* **What happened in the last extraction?** Open the **Recent Extractions** filter and click the relevant extraction to scope Workflow Tasks to that run instantly.
* **Is provisioning running now?** Check the **Workflow Tasks** stats card at the top of the page. The Scheduled, Waiting, and Running totals update live without any filtering.
* **Troubleshoot a failed action**: Go to the **Integration Jobs** tab, filter by **State = Errored**, and open the failed job. Switch to the **Workflow Actions** tab for context on the broader operation that spawned the failing jobs. See [Explain Run Errors with Access AI](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/how-to/explain-run-errors-with-ai.md) for an AI explanation of the failure.
* **Export activity for compliance**: On the **Events** tab, use the export button to download a CSV or PDF. Activity logs are retained indefinitely, even if the associated integration is later removed.

### Log Retention and Security

Veza maintains all Lifecycle Management activity logs for audit purposes. These logs are retained even if the associated integration is removed, maintaining a full historical record of all provisioning operations.

> **Note**: Events shown on the Provisioning Activity page are distinct from the system-wide Event Logs found in the Veza Administration section.

### Best practices

#### Review timing

Review the Provisioning Activity page after extractions complete to verify expected workflow execution. For large policies, trigger evaluation and workflow execution can take several minutes to complete. Allow time for processing before reviewing activity.

#### Custom monitoring dashboards

For advanced monitoring requirements, you can build custom dashboards using Veza's query and dashboard features to track LCM policy health metrics. Contact Veza Support for guidance on building LCM-specific monitoring dashboards for your deployment.


---

# 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/getting-started/activity-log.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.