Configure a Profile Action
Add a Profile action to profile a datastore's tables automatically whenever the Flow's trigger activates, building field metadata and, if you enable AI Effort, inferring quality checks.
Permission Required
You need the Manager role to edit and publish Flows. See Flow Permissions for details.
Initialized datastores only
Only initialized datastores appear in the Datastore dropdown. A source datastore becomes initialized after successful Sync, Profile, and Scan runs. An enrichment datastore becomes initialized after Sync and Profile.
Field reference
The Profile Settings panel shows the following fields. They mirror the options of running the operation directly on the datastore.
Select the datastore first
The sections below live in the Operation Configuration stepper and stay disabled until a Datastore is selected. For DFS datastores, the Select step lists File Patterns instead of Tables.
| Field | Required | Type | Description |
|---|---|---|---|
| Datastore | Option | The source datastore to profile. |
Select Tables
Choose which tables the profile covers. Picking one of the options is required to move to the next step, and All is preselected.
Read Settings
| Field | Required | Type | Description |
|---|---|---|---|
| Record Limit | Number | The maximum number of records to profile per table, after any initial filtering. Pick a preset (1M, 10M, 100M, or All) or type a custom value from 1 to 1,000,000,000. Defaults to 100M. |
Starting Threshold
Optionally set a minimum incremental identifier value as the starting point for the profile. Turning on the Starting Threshold toggle reveals the fields below.
Greater Than Batch depends on the datastore
Greater Than Batch only appears for datastores backed by a database connector (JDBC and native connectors). DFS datastores never show it.
| Field | Required | Type | Description |
|---|---|---|---|
| Greater Than Time | Timestamp | The starting timestamp, in UTC. Applies only to tables with an incremental timestamp strategy. | |
| Greater Than Batch | Number | The starting batch value, 0 or higher. Applies only to tables with an incremental batch strategy. |
AI Management
The Effort slider and the Oversight checkbox both start on the selected datastore's own defaults.
| Field | Required | Type | Description |
|---|---|---|---|
| Effort | Slider | How much effort the AI puts into generating checks: Off, Low, Medium, High, Extra High, or Max. It starts on the datastore's own default effort. Higher effort considers broader categories of patterns, applies deeper analysis, and takes longer to complete. | |
| Activate AI managed checks | Checkbox | Whether the AI managed checks the profile creates are activated automatically or created as drafts for review. It starts on the datastore's own default, and is disabled when Effort is Off. |
Steps
Step 1: Navigate to the Flows page by clicking Flows on the left side panel.
Step 2: On the Definitions tab, click the Flow. On its canvas, click the dashed Action placeholder after the trigger, or the + handle at the bottom edge of a node.
Step 3: In the List of Actions panel, pick the Operation category, then click Profile. The Profile Settings panel opens on the right-hand side.
Step 4: Fill in the fields.
Step 5: Click Save. The node shows a CHANGED badge and the You have unpublished changes banner appears on the canvas.
Step 6: Click Publish to make the action live.