Desktop flow action logs configuration

This article provides configuration guidance for desktop flow logs, located under the environment's feature section in the Power Platform admin center and in Power Automate for verbosity configuration of specific flows.

The Activation status of run action logs setting defines when desktop flow run action logs should be captured and even allows you to turn them off completely.

Prerequisites

• Premium Power Automate license and administrative privileges to configure log settings
• Power Automate URL and IP address configurations
  • Public cloud
  • Government cloud

Configure desktop flow action log version

Use the Action logs version setting to choose V1, V2, or both.

The FlowLogs entity time to live in minutes value determines how long action logs are retained in the Flow Logs elastic table. Dataverse automatically deletes records that are older than the specified time frame. Here are some example values for your convenience.

Key differences between desktop flow logs V1 and V2

The following table describes the differences between desktop flow logs V1 and V2:

Logs V2 offers significant enhancements over the previous version, V1. V2 uses the elastic tables feature, which is great for handling large data volumes, like action log scenarios, and has built-in data retention (TTL). It's ideal for organizations needing to access significant amounts of data for reporting, governance, and integration with automatic data retention control.

Dataverse capacity demand calculations for logs V2

The following table shows sample Dataverse log storage consumption estimates per desktop flow run when using logs V2. It outlines the approximate storage demand for different numbers of actions, assuming an average of 3 KB of storage per action.

Action logs verbosity

Desktop Flow Logs V2 lets you set verbosity levels to balance observability and storage efficiency. Each level controls how much detail logs show during flow execution. This section describes the available verbosity levels for desktop flow action logs, how to configure them at the environment level in Power Platform Admin Center (admins only), and how to configure them for individual desktop flows.

Verbosity levels in desktop flow action logs

Configure action log verbosity in the Power Platform Admin Center (Admin only)

Admins can set the default verbosity level for an entire environment. This setting applies to all desktop flows unless overridden at the flow level.

1. Sign in to the Power Platform Admin Center.

2. In the navigation pane, select Manage.

3. In the Manage section, select Environments and then select the environment where your desktop flows run.

4. Select Settings.

5. Expand Product and select Features.

6. Locate the Action logs verbosity setting in the Desktop flow run action logs configuration section.

7. Choose your default level: Error, Warning, Custom, Debug, or Full.

8. Select Save to apply the configuration.

   

Configure action log verbosity for a specific desktop flow

Makers can configure verbosity for each desktop flow from the Power Automate portal. This local setting overrides the admin default.

Override the environment setting when you need to:

• Debug a specific desktop flow without increasing logs for the entire environment.
• Temporarily increase verbosity during testing or troubleshooting.

Follow these steps to configure action log verbosity for a specific desktop flow:

1. Sign in to Power Automate.
2. Open the flow details page of the desktop flow you want to configure.
3. Select Edit and locate the Action logs verbosity section.
4. Select the desired verbosity level for this specific flow.

1. Save your changes.

Query data logs V2

You can access desktop flow action logs data by making an API call to the Dataverse backend. You can use the traditional API call syntax or the new ExecuteCosmosSqlQuery method. By using this method, you can execute a SQL query against Dataverse, which enables you to retrieve and filter data.

The data logs model V2 is based on a parent-child relationship between the flow session and flow log tables. Every record inherits permissions from its parent flow session record. To query action logs of a specific desktop flow run, use the following query syntax.

Traditional Dataverse API call syntax

The following API call retrieves a specific flow session by its ID (aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb) and then accesses the associated action logs through the flowsession_flowlog_parentobjectid relationship.

[Organization URI]/api/data/v9.0/flowsessions(aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb)/flowsession_flowlog_parentobjectid  

New ExecuteCosmosSqlQuery API call syntax using FlowLogs table

    [Organization URI]/api/data/v9.2/ExecuteCosmosSqlQuery(
    QueryText=@p1,EntityLogicalName=@p2,QueryParameters=@p3,PageSize=@p4)?
    @p1: 'SELECT c.props.flowlogid as flowlogid, c.props.createdon as createdon, c.props.data as data, c.props.level as level, c.props.type as type, c.ttl as ttlinseconds, c.props.cloudflowid as cloudflowid, c.props.cloudflowrunid as cloudflowrunid, c.props.desktopflowid as desktopflowid, c.props.flowmachineid as flowmachineid, c.props.flowmachinegroupid as flowmachinegroupid, c.props.flowsessionid as flowsessionid, c.props.workqueueid as workqueueid, c.props.workqueueitemid as workqueueitemid FROM c WHERE c.props.type IN (100000001) ORDER BY c.props.data.startTime DESC'
    @p2: 'flowlog'
    @p3: {"Keys":["@referencingParentId","@referencingParentLogicalName"],"Values":[{"Type":"System.Guid","Value":"40590757-a9c0-4f4c-abfc-e2f389049d90"},{"Type":"System.String","Value":"flowsession"}]}
    @p4: 50

Learn more about querying JSON columns in elastic tables.

Breaking down the call into individual pieces

• The base URL (https://[my org].api.crm[my region].dynamics.com/api/data/v9.2/) is the endpoint for the Dataverse Web API.
• ExecuteCosmosSqlQuery is the method you're calling. This method runs a SQL query against Dataverse.
• The parameters for the ExecuteCosmosSqlQuery method are provided in parentheses following the method name:
  • QueryText=@p1: The SQL query to run. This query selects various properties from a table where the type is 100000001 (desktop flow action log type) and orders the results by the startTime property in descending order.
  • EntityLogicalName=@p2: The logical name of the table (flowlog) that stores the action logs.
  • QueryParameters=@p3: A JSON object specifying parameters for the query. In the previous example, it specifies a key-value pair where the keys are @referencingParentId and @referencingParentLogicalName with values of flowsessionid (GUID) and type of the table flowsession.
  • PageSize=p4: The query page size.

Known limitations

• Logs V2 are only available for desktop flow runs that the user starts from a cloud flow through the desktop flow connector action.
• Bulk-delete jobs aren't currently supported for the Flow Log table.
• You can't view flow log records yet in the Table section of the Power Apps maker portal.
• Changing action log version doesn't migrate previous desktop flow action logs to the new log storage type.
• Don't use the FlowRun and FlowLog entities as targets for the When a row is added, modified or deleted flow trigger. Using these entities as targets might cause an infinite loop because the system creates records in these tables every time a flow runs.