Configuring Compliance Form Completion Notifications via GraphQL Workaround – DataHub Customer Support Portal

Area: Product Issues

Sub-Area: Compliance Forms / Notifications

Issue

Some DataHub documentation references a "Configure notification triggers (form assigned, form completed, etc.)" step when setting up compliance workflows. Users attempting to follow this guidance cannot locate any setting in the UI or API to trigger a notification when a compliance form is completed on an asset. This is a documentation inaccuracy: as of the current release, DataHub only sends a notification to assignees when a form is published — there is no built-in trigger for form completion. Users who require an alert or automated event when all required fields on a compliance form are filled in must implement a workaround using the GraphQL completedForms search filter.

Error Messages

No notification trigger for "form completed" found in Settings or Govern → Compliance Forms UI

You Might Be Asking

Where do I configure a notification to fire when a compliance form is completed?
Why can't I find "notification triggers" under Settings → Forms as described in the documentation?
Is there a way to alert a team or group when all assignees finish a compliance form on a dataset?
How do I detect newly completed compliance forms programmatically in DataHub?

Solution

There is currently no native UI or API setting to send a notification when a compliance form is completed. The only built-in compliance form notification DataHub sends is to assignees at the time a form is published. The steps below explain the current notification behavior and document the recommended workaround for detecting form completions and routing alerts externally.

Understand the current notification behavior.
Compliance forms are managed under Govern → Compliance Forms (not "Settings → Forms" as some older documentation states). When a form is published and assigned, DataHub notifies assignees via email, Slack, and the Task Center — provided the formsNotificationsEnabled feature flag is active on your instance and users have configured their personal notification preferences under Settings → Personal → Notifications → Compliance Forms. The only supported trigger is Form Published; there is no Form Completed trigger available in the UI.
Confirm the feature flag is enabled (DataHub Cloud).
If the publish-time notification options are not visible in your form editor, the formsNotificationsEnabled feature flag may not be active for your instance. Contact DataHub Support to verify and enable this flag for your deployment before troubleshooting further.

Use the completedForms GraphQL filter to detect completed assets.

Completion state is recorded on each asset. You can query which assets have completed a specific form by filtering on the completedForms field in a searchAcrossEntities call. Replace <your-form-urn> with the URN of your compliance form.

{
  searchAcrossEntities(input: {
    query: "*",
    start: 0,
    count: 100,
    orFilters: [
      {
        and: [
          {
            field: "completedForms",
            values: ["<your-form-urn>"]
          }
        ]
      }
    ]
  }) {
    total
    searchResults {
      entity {
        urn
      }
    }
  }
}

Query for incomplete assets using the incompleteForms filter.

To see assets where the form is still outstanding, swap the field name:

{
  searchAcrossEntities(input: {
    query: "*",
    start: 0,
    count: 100,
    orFilters: [
      {
        and: [
          {
            field: "incompleteForms",
            values: ["<your-form-urn>"]
          }
        ]
      }
    ]
  }) {
    total
    searchResults {
      entity {
        urn
      }
    }
  }
}

Schedule the query and diff results to detect new completions.
Run the completedForms query on a schedule (for example, via a cron job, Airflow DAG, or similar scheduler). Store the list of returned URNs from each run. Any URN present in the current run but absent from the previous run represents a newly completed form. Pass these new URNs to your external notification system (email, Slack, PagerDuty, etc.) to alert the appropriate team or group.

A minimal pseudo-code pattern:
```
# Pseudocode — adapt to your preferred language and scheduler

previous_urns = load_from_store("completed_urns_previous_run")
current_urns  = set(run_graphql_query(completedForms_query))

newly_completed = current_urns - previous_urns

if newly_completed:
    send_alert(
        recipients=["team-group@example.com"],
        message=f"The following assets completed the compliance form: {newly_completed}"
    )

save_to_store("completed_urns_previous_run", current_urns)
```
Locate your form URN.
If you do not know the URN for your compliance form, navigate to Govern → Compliance Forms, open the form, and inspect the page URL or use the following GraphQL query to list all forms and their URNs:
```
{
  listForms(input: { start: 0, count: 50 }) {
    forms {
      urn
      info {
        name
      }
    }
  }
}
```

Additional Notes

This behavior was confirmed on DataHub Cloud versions up to and including v2.3.6. The only compliance form notification trigger available in that version is FormNotificationSettings.notifyAssigneesOnPublish (template type BROADCAST_COMPLIANCE_FORM_PUBLISH). No completion trigger exists at the code level as of that release.
A native form-completion alert (email or Slack notification to a group, optionally as a daily summary) has been submitted as a feature request to the DataHub Product team. There is no committed timeline. If this capability is critical to your planning, raise priority with your Customer Success Manager.
Some older documentation incorrectly lists "Settings → Forms" as the navigation path and implies a "form completed" notification trigger exists. The correct path is Govern → Compliance Forms. The documentation inaccuracy is a known issue.
Microsoft Teams is not supported as a notification channel for compliance form notifications; only Email and Slack are supported for the publish-time trigger.
The formsNotificationsEnabled feature flag must be active on your DataHub Cloud instance for any compliance form notification UI options to appear. If the UI options are missing, contact DataHub Support.
The GraphQL searchAcrossEntities endpoint used in this workaround is paginated. If your catalog contains a large number of assets assigned to the form, increment the start offset and repeat calls until total results are retrieved.

Issue

Error Messages

You Might Be Asking

Solution

Additional Notes

Related Documentation