Monitoring runs of enrichment jobs

Viewing job run details

In general, you can access any job run details from the Jobs page in a project:

1. You can select the job for which you want to review the run information and details from this page. If you have many jobs, you can scope the view:

   • Jobs with active runs
   • Active runs
   • Jobs with finished runs
   • Finished runs

   You can further narrow down the search results for the selected view scope by applying more filters.

2. Click the job name. The job details page shows the number of completed and failed runs, and the configured job schedule.

3. Select a particular run and review the run details. The following run details are provided for a job run if you access the run details from the metadata enrichment by using the View metrics link:

   • The job run status
   • The duration, start and end times
   • Who started the run
   • A link to the associated job
   • A link to the associated metadata enrichment
   • Basic information about the enrichment configuration:
     • The selected enrichment options
     • The number of categories to use for data class, term, and classification assignment
     • The sampling method used
     • The algorithms that are used for term assignment

   Here, you can also pause and resume the job run.

You can also access the details for the most recent metadata enrichment job run from the metadata enrichment asset. You can click the View metrics link in the Job details section in the information panel or the Details of job run link in the asset details panel.

Viewing run metrics

Run metrics are provided for metadata enrichment jobs that are run as configured or that are run for advanced data profiling. On the Run metrics tab in the job run details, you can monitor the progress of an active run of the metadata enrichment job or check the status information for a completed job run.

Run metrics are available only for jobs that were run after November 21, 2025. For older job runs, you can check the job run log.

The Summary section shows the overall progress of the enrichment:

• The total number of assets that are enriched.
• The numbers of completed, in progress, and failed assets. For failed assets, a link to the failure details is provided.
• The percentage of assets for which enrichment is done.

The metrics for the Analyze relationships task are calculated differently than the other task metrics. Therefore, they are not reflected in the summary.

The Objectives section shows the progress for the individual enrichment options in the order in which they are processed. Data quality analysis, if selected, is run as part of profiling and is not shown separately.

In addition to the progress bar for the overall process of each enrichment task, you can see how many data assets are in which status while the task is processed. Except for the Analyze relationships task, a data asset have these statuses:

• In progress: The asset is being processed or waiting to be processed.
• Completed: The enrichment task is successfully completed for the asset.
• Skipped: The asset was not processed because a prerequisite enrichment task failed. For example, term assignment might require profiling depending on the selected algorithms. During profiling, assets cannot have this status because profiling is usually the first step in an enrichment process.
• Failed: The enrichment task failed for the asset. If the count is not zero, you can click the number to see details about the failures.

For the the Analyze relationships enrichment objective, the total number of tasks, the number of completed tasks, and the number of tasks with errors are shown. The total number of analysis tasks depends on the number of data assets that are analyzed. For every 1,000 data assets, an analysis task is created for calculating potential relationships.

For paused enrichments, the metrics on the dashboard are hidden for the time of the pause. On resuming the enrichment, the initial metrics reflect the enrichment status at the point of pausing the enrichment. While a job run is paused, the log might provide more detailed information about the actual status than the metrics dashboard.

For canceled enrichments, the metrics reflect the enrichment status at the point when the run was canceled. The actual enrichment result can differ from the shown metrics because enrichment of assets with the status in progress might still be completed after the job was canceled. Whether enrichment of an in-progress asset is canceled or completed depends on the asset's internal processing status. The log might provide more detailed information about the actual status than the metrics dashboard.

Understanding the job run log

Logs are provided for all types of metadata enrichment jobs. To view the log for a job run, switch to the Log tab on the Job run details page. The log shows the job type, the job run ID, and details depending on the enrichment tasks.

• The entry Full metadata enrichment job run or Delta metadata enrichment job run indicates a basic metadata enrichment job that is run with the configured enrichment options. Full means that the enrichment is run on all data assets in the scope or on a manually selected set of data assets. Delta means that only those data assets are enriched that were added or modified after the last run of the enrichment, or for which the previous enrichment failed or was canceled. The Data scope of reruns determines whether a full or a delta metadata enrichment is run.

  For a metadata enrichment job, similar information as in the metrics dashboard is shown, such as an asset summary and statistics for each enrichment task. In addition, some details about the used term assignment model are included if term assignment is part of the enrichment.

  You can pause and resume runs of this job type. The job run log then contains an entry that shows the start and end time of the pause. Only the last pause is listed in the log even if the job run was paused several times.

• The entry Advanced profiling metadata enrichment job run indicates a job for generating more accurate profiling results. In the metrics dashboard, this type of job run is shown as Profile data task.

• The entry Key analysis job run indicates a job for key or relationship analysis. The type of analysis is identified by one of these entries:

  • Primary key detection task (<taskID>) of type 'pk_deep'
  • Foreign key relationship detection task (<taskID>) of type 'fk_deep'
  • Overlap key detection task (<taskID>) of type 'overlap'

  No run metrics are provided for this job type.

• The entry Metadata publish job run indicates a publish job.

Parent topic: Managing enrichment jobs