Tools → Load Job Details Viewer

About the Load Job Details Viewer

The Load Job Details Viewer is available to schema managers to review the status and history of a load job or a load plan. By default, the Load Job Details Viewer shows the schemas, objects, and details of a load job. In addition, it lists the history of the related load jobs.

Note

The Loader Service executes each group in the load plan as a separate load job. The Load Job Details Viewer separately shows the details of each group.

Load Job Details Viewer access rights

A Super User or a user that belongs to a group with the SuperRole or Schema Manager role can access the Load Job Details Viewer to view the details of load jobs related to schemas that the user owns or has access rights to. When the Cluster Management Console (CMC) admin turns the Enable Super User Mode option on, the Super User and users with the SuperRole can access the Load Job Details Viewer of all load jobs regardless of the access rights to the related schemas.

You can access the Load Job Details Viewer as follows:

In the navigation bar, select Schema, select the Load Jobs tab, and then select a load job.
In the navigation bar, select Schema, and then on the Schemas tab, select the status or time of the latest or current load job.
In the navigation bar, select Schema, and then on the Schemas tab, select a schema. On the Schema Designer, select the status or time of the latest or current load job.
On the Home page, select the Job Details of a failed, interrupted, or finished with errors job. (available on Cloud installations only)

If the latest or current load job is related to a single-group load plan, the Load Job Details Viewer by default filters the schemas list to show the relevant schema only. And if the latest or current load job is related to a multi-group load plan, the Load Job Details Viewer by default expands the group with the selected schema, collapses other groups, and filters the group schemas to show the relevant schema only. You can remove or update the filters and expand other groups to view other schemas in the load plan.

Enhancements introduced in the Load Job Details Viewer

Shows single-schema and multi-schema jobs.
Shows and differentiates between scheduled and manual schema jobs
Shows the total rows per object
Shows the tool used to invoke the job

Note

A manual load job is one that users invoke either using the application UI (via the Schema Designer or the Scheduler > Load Plans) or an API endpoint.
A scheduled load job is one that the Scheduler runs depending on load plans with one or more physical schemas.

Anatomy

The Load Job Details Viewer consists of the following:

Page header
Load job history
Load job details

The page header shows the following:

Breadcrumb navigation
The schema or load plan name
The last sync time of the load jobs and details, and a Refresh button to manually refresh them

Load job history

This part shows the history of load jobs related to the job that you select on the Load Jobs list.

If you select a load job of a scheduled load plan with multiple schemas, this list shows all the load jobs of this load plan, that is, the runs of this scheduled load plan.
If you select a load job that you or another user manually started for a specific physical schema (via the application UI or API calls) or a load job of a scheduled load plan with a single schema, the list shows:
- All manual load jobs of this physical schema, including those that other users invoked, whether via the application UI or API calls.
- Load jobs of all load plans with this single schema.

The load job history list shows the following details for each load job:

Status (icon): You can filter the job list by the job status.
Job Starting Time: The job start time. By default, the list is sorted in descending order according to the job start time.
Duration: The time elapsed during the load job. You can sort the list according to the load job duration. The duration of each stage in the load job is visualized using a colored bar. If the load plan includes multiple groups, the colored bar can be repeated according to the number of groups executed in the load plan as each group is considered as a separate load job.

Note

If a group load job fails due to a Loader Service issue, and the Loader Service retries to load the same group again, this group will appear twice on the object list, and the number of groups will be increased by one.

The history list shows the recent 50 load jobs, you can navigate to earlier jobs using the page controls. Additionally, you can collapse the history pane to allow more space for the job details part.

The impact of deleting a schema

When you delete a physical schema, the following applies:

Manually started jobs will be deleted and won't appear on the list.
Load jobs of single-schema load plans with this schema won't be deleted.
Load jobs of multi-schema load plans with this schema won't be deleted.

Load job details

This section displays detailed information about the selected job, including associated load plan groups (if applicable), physical schemas, and objects. By default, it shows the details of the job selected in the Load Jobs list, or the most recent load plan when you access the Load Job Details Viewer from other pages such as Schema Manager, Schema Designer, or the Home page.

You can select a different job at any time to view its corresponding details.

This part contains the following:

The summary section
The Start menu
The search box
View options
The Details list

Summary section

This summary of the selected job shows the following:

The start time of the selected load job or load plan execution
Execution time, groups, and schemas for multi-group plans:
- The total number of groups and schemas in the load plan, in addition to the elapsed time or total execution time (in the case of in progress, finished with error, or successful plan executions)
- The number of groups and schemas that have been executed only (in the case of an interrupted or failed load plan)
The load job or plan status
The execution type: manual or scheduled
The load plan name (in case the selected job is part of a load plan execution)

Starting 2024.7.x, you can manually start or restart a load plan from the Load Job Details Viewer page. You can start or restart the execution of the whole load plan or from a specific group. This is helpful especially when the execution of a load group fails. The Start option is available for completed load plans only when you select the latest job executed for a load plan on the history pane. This option is not available for load plans with a running job.

Note

When you select to restart the load plan execution from a specific group, the subsequent groups in the load plan are executed as well.

Here are the steps to start the execution of a load plan:

On the Load Jobs tab, select a completed load job for a load plan.
On the Load Job Details Viewer, select Start > Start.

Here are the steps to restart the execution of a load plan:

On the Load Jobs tab, select a completed load job for a load plan.
On the Load Job Details Viewer, select Start > Restart from....
In the Restart from ... dialog, select the load group from which you want to restart the execution of the load plan.
- In the case of failed or finished with errors load groups, turn the Run failed steps only toggle on to restart the execution of the load plan from the point of failure of the selected failed or finished with errors load group, skipping successful extraction and enrichment tasks. Subsequent load groups will start from the beginning as usual.
  Note
  - The Run failed steps only option is available starting with 2025.7.1.
  - Recovering failed steps requires turning on the Enable detailed load jobs tracking option in Server Configurations > Incorta Labs.
Select Done.

Use the search box to search for schemas or objects in the details table. Only matching schemas or objects are displayed on the details list.

View options

Before 2025.7.1, you can view the details of the load job or plan execution in a grid view only. In this view you can control the columns displayed on the details list using the Show/Hide Columns menu. Your column selection is cached in the browser.

Starting with 2025.7.1, a Gantt chart view is available, which provides a visual timeline of load job execution.

Details list

The details list shows a summary row for each load job and the loading details of the included schemas and objects.

Job summary

A summary row is displayed per load job. As the execution of a group in a multi-group load plan is handled as a separate load job, a summary row is displayed per group.

The summary row displays the following details per load job:

The group number, if applicable
The group loading status, if applicable
The total duration of the load job (The duration of each stage is visualized using a colored bar.)
The duration of each stage: In Queue, Planning, Running, and Post-load
Note
Starting with 2026.2.0, Post-load calculations are no longer handled as a separate stage and are now included within the Running phase. You can review the Running phase breakdown, including Extraction, Deduplication, Load, and Post-load, by selecting the magnifier icon next to the Running duration.
The number of schemas and objects in the load job
The number of extracted and enriched objects in case of a running job
The total number of rejected rows, if any

Schema and object loading details

This list is repeated according to the number of load groups. It is displayed either in a grid view or Gantt chart, showing the details for each object in the load job.

Grid view

In the case of a grid view, the details list shows the following:

Column	Description
Schema / Table	Select the schema name to expand or collapse objects in the schema. This list is collapsed by default and is sorted in ascending order by the schema name, and within each schema, objects are sorted alphabetically. This column is frozen when you scroll horizontally across the details.
Load Type	The load type per schema or object: ● F for full load ● I for incremental load ● S for load from staging ● P for data purge jobs (starting 2024.7.x)
Extraction/Enrichment > Start	The start time of the object extraction or enrichment
Extraction/Enrichment > Duration	The elapsed time during the object extraction or enrichment
Extraction/Enrichment > Extracted	The number of rows extracted or enriched for this schema or object during this load job, including the rejected rows
Extraction/Enrichment > Rejected	The number of rejected rows during the extraction or enrichment per schema or object
Purge > Start	Available starting 2024.7.x in the case of a data purge job, representing the start time of the data purge process of the respective object. Displays `-` in the case of objects that do not have configurations for data retention or exclusion or inclusion sets.
Purge > Duration	Available starting 2024.7.x in the case of a data purge job, representing the elapsed time during the data purge process of the respective object. Displays `0` in the case of objects that do not have configurations for data retention or exclusion or inclusion sets.
Deduplication > Start	Available starting with 2024.1.x. The start time of the deduplication phase, which includes the PK-index creation and Parquet compaction processes.
Deduplication > Duration	Available starting with 2024.1.x. The elapsed time during the deduplication phase.
Load/Post-Load > Start	The start time of loading the object into the Engine memory. All Load/Post-Load columns will show no data for non-performance-optimized objects.
Load/Post-Load > Duration	The elapsed time to complete the Load/Post-Load calculations for the respective object
Load/Post-Load > Loaded	The number of rows loaded during the selected load job per schema or object including those: ● Loaded from the extracted/enriched rows. ● With duplicates in the memory. ● That failed to load during previous load jobs and were loaded during the selected load job.
Load/Post-Load > Total Rows	The total number of unique rows loaded into the Engine memory for the respective schema or object after the selected load job, including rows loaded during previous load jobs and the selected load job. This number might be different from the current total number of rows loaded for the related schema or object. For non-performance-optimized objects, the total rows are 0 as no rows from this object are loaded into the Engine memory.
Send to Destination > Start	The start time of sending the object to configured data destination.
Send to Destination > Duration	The elapsed time to complete the Send to Destination calculations for the respective object.
Send to Destination > Sent Rows	The number of rows sent during the selected load job per schema or object
Send to Destination > Total Rows	The total number of rows at the data destination per schema or object after the rows were sent. You can always compare the total numbers in the data destination with the total number of rows in each loading phase.
Status	The load status per schema or object This column is frozen when you scroll horizontally across the details. Starting with 2025.7, when you hover over the status of a successful MV load, you can download the MV logs. However, for failed MVs, select the Failed status to review the error and download the logs. For more details, refer to Materialized View > MV logs.

Notes

By default, the details list is sorted per group in ascending order by the schema name. You can use all columns to sort this list per group, except for the Load Type column. Sorting is applied to all rows in the load group. As a result, the group schemas are expanded, and the schema name might appear multiple times on the sorted list. When you select the header of a column, the list is sorted in ascending order by this column; select it again to sort it in descending order. Selecting the same column header for the third time resets the list sorting.
You can use the Schema/Table, Load Type, and Status columns to filter out the schemas and objects that appear on this list. Starting with 2024.1.x, used filters are preserved when refreshing the details list.
The total number of rows differs according to the loading type whether it is incremental, full, or staging load. The load job sends the data to destination only if you are using full or incremental load. Also, the Send to Destination section is only available if you have a data destination set for one or more schemas in the load job.

Gantt chart view

The Gantt chart view is available start with 2025.7.1, providing a visual timeline of load job execution. Objects are displayed on the vertical axis with tasks shown along a horizontal timeline, making it easier to monitor task progress and sequence. This update also introduces detailed visualization of data extraction durations to help identify performance bottlenecks.

In the Gantt chart view, you can:

Offset the graphs by the starting time for better comparison.
Sort the objects on the vertical axis by schema name, table name, start time, or duration.
Filter the chart by duration.
Filter the chart by task: Extraction/Enrichment, Deduplication, and Load/Post-Load.

Additional information

Data Purge

The Data Purge job is available starting 2024.7.x to delete the object's Parquet data that falls under one of the following:

Does not satisfy the data retention conditions.
Matches the exclusion set for the physical table or MV.
Does not exist in the inclusion set for the physical table or MV. (Available starting 2026.2.0)

Schema objects with no data retention, exclusion set, or inclusion set configurations are loaded from staging during a data purge job.

For details about data retention, exclusion sets, and inclusion sets, refer to Table Editor → Advanced Settings.

Errors and logs

If a multi-group load job fails or finishes with errors, when you select the status, the error message shows the status of each group that causes the errors. When you select the status of the group on the objects list, the error message shows the error per object with a link to view the error details.

If a multi-group load job is interrupted:

The job status of the whole load plan will be Interrupted.
The job status of the group that is running when you stop the job will be Interrupted.
Finished groups in the load plan will not be impacted by stopping the running job and will have their own status.
Groups that have not started yet will not appear on the Load Job Details Viewer.