> 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 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: *Events*, *Jobs*, *Actions*, and *Workflow Tasks*. #### Workflow Tasks stats card When the page opens, a **Workflow Tasks** stats card shows live counts for the last 24 hours: **Scheduled**, **Queued**, **Running**, **Done**, and **Errored**. Use this card to get an at-a-glance health check without applying any filters — Scheduled and Queued 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 | | Entity Name | The name of the entity affected by the event | | Entitlement Entity | The entitlement entity involved in the event, if applicable | | Message | Additional details or error messages related to the event | #### Jobs Tab The 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 | | ------------- | ------------------------------------------------------------------ | | Started At | When the job started | | Completed At | When the job completed | | Action Name | The name of the action that initiated the job | | Action Type | The type of action (e.g., SYNC\_IDENTITIES, MANAGE\_RELATIONSHIPS) | | 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 | | Error Message | Detailed error information if the job failed | #### Actions Tab The 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 | | ------------ | ------------------------------------------------------------------ | | Started At | When the action started | | Completed At | When the action completed | | Action Name | The name of the action | | Action Type | The type of action (e.g., SYNC\_IDENTITIES, MANAGE\_RELATIONSHIPS) | | 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 | 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 | | ------------------ | --------------------------------------------------------------------------------------------------- | | Workflow | The name of the workflow | | Identity | The identity for which the workflow was executed | | Scheduled For | When the workflow was scheduled to run, if applicable | | Started At | When the workflow started | | Completed At | When the workflow completed | | Entity Type | The type of entity processed by the workflow | | State | The current state of the workflow (Completed, Errored) | | Manually Triggered | Whether the workflow was triggered manually (**Yes**) or by an automatic policy evaluation (**No**) | | Messages | Additional details or error messages related to the workflow | ### 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 in the Activity Log ### 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**: Review issues by checking for error messages in the Message column ### 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 right now?** Check the **Workflow Tasks** stats card at the top of the page — Scheduled, Queued, and Running counts update live without any filtering. * **Troubleshoot a failed action**: Go to the **Jobs** tab, filter by **State = Errored**, and read the **Error Message** column. Switch to the **Actions** tab for context on the broader operation that spawned the failing jobs. * **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](https://support.veza.com) 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/getting-started/activity-log.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.