Check the status of a workflow (Preview)

When a workflow is created, it's important to check its status, and run history to make sure it ran properly for the users it processed both by schedule and by on-demand. To get information about the status of workflows, Lifecycle Workflows allows you to check run and user processing history. This history also gives you summaries to see how often a workflow has run, and who it ran successfully for. You're also able to check the status of both the workflow, and its tasks. Checking the status of workflows and their tasks allows you to troubleshoot potential problems that could come up during their execution.

Run workflow history using the Azure portal

You're able to retrieve run information of a workflow using Lifecycle Workflows. To check the runs of a workflow using the Azure portal, you would do the following steps:

  1. Sign in to the Azure portal.

  2. Select Azure Active Directory and then select Identity Governance.

  3. On the left menu, select Lifecycle Workflows (Preview).

  4. On the Lifecycle Workflows overview page, select Workflows (Preview).

  5. Select the workflow you want to run history of.

  6. On the workflow overview screen, select Audit logs.

  7. On the history page, select the Runs button.

  8. Here you'll see a summary of workflow runs. Screenshot of a workflow Runs list.

  9. The runs summary cards include the total number of processed runs, the number of successful runs, the number of failed runs, and the total number of failed tasks.

User workflow history using the Azure portal

To get further information than just the runs summary for a workflow, you're also able to get information about users processed by a workflow. To check the status of users a workflow has processed using the Azure portal, you would do the following steps:

  1. In the left menu, select Lifecycle Workflows (Preview).

  2. select Workflows (Preview).

  3. select the workflow you want to see user processing information for.

  4. On the workflow overview screen, select Workflow history (Preview). Screenshot of a workflow overview history.

  5. On the workflow history page, you're presented with a summary of every user processed by the workflow along with counts of successful and failed users and tasks. Screenshot of a list of workflow summaries.

  6. By selecting total tasks by a user you're able to see which tasks have successfully completed, or are currently in progress. Screenshot of workflow task history status.

  7. By selecting failed tasks, you're able to see which tasks have failed for a specific user. Screenshot of workflow failed tasks history.

  8. By selecting unprocessed tasks, you're able to see which tasks are unprocessed. Screenshot of unprocessed tasks of a workflow.

User workflow history using Microsoft Graph

List user processing results using Microsoft Graph

To view a status list of users processed by a workflow, which are UserProcessingResults, you'd make the following API call:

To view a list of user processing results using API via Microsoft Graph, see: List userProcessingResults

User processing results using Microsoft Graph

To view a summary of user processing results via API using Microsoft Graph, see: userProcessingResult: summary

Run workflow history via Microsoft Graph

List runs using Microsoft Graph

To view runs of a workflow via API using Microsoft Graph, see: runs

Get a summary of runs using Microsoft Graph

To view run summary via API using Microsoft Graph, see: run summary of a lifecycle workflow

List user and task processing results of a given run using Microsoft Graph

To get user processing result for a run of a lifecycle workflow via API using Microsoft Graph, see: Get userProcessingResult (for a run of a lifecycle workflow)

To list task processing results for a user processing result via API using Microsoft Graph, see: List taskProcessingResults (for a userProcessingResult)

Note

A workflow must have activity in the past 7 days to get userProcessingResults ID. If there has not been any activity in that time-frame, the userProcessingResults call will not return a value.

Next steps