Job history
- Last UpdatedMar 12, 2026
- 2 minute read
You can view the job history of your virtual tables in CONNECT data services. You can diagnose issues and look at specific information such as job type, the state of your jobs, and the time in which a job was previously run.
View jobs
-
In the left pane, select Analytics > Virtual Tables.
-
Select the Jobs History tab.
-
Select a job to view.
The side sheet appears.
-
The side sheet includes the following information:
-
Virtual table name, virtual table ID, and job run ID.
-
The previous job interval and status of the last refresh.
-
The most recent job update and the status of the update.
-
-
Select the filter icon
to filter by Virtual Table ID or State.
Data gaps
The data gaps column shows a status update if there is an issue with a job that is resulting in a data gap. The following statuses are possible:
-
Active data gap: a data gap exists and requires user action.
-
Resolved by job: a later successful job automatically resolved the gap.
-
Dismissed by user: a user acknowledged and dismissed the data gap.
-
Partially resolved: a job resolved only part of a gap interval.
-
Refreshed: a manual refresh job resolved the gap.
If the Data Gaps column is empty, there are no current issues.
To resolve a data gap, do the following:
-
In the left pane, select Analytics > Virtual Tables.
-
Select the Jobs History tab.
-
Select a job that has a data gap error.
The side sheet appears.
-
Select More Options
.
-
Select Refresh Data Gap to refresh the job.
-
Select Dismiss Data Gap to dismiss the error without refreshing the job.
-
Job types
The following job types are available for virtual tables.
|
Job Type |
Description |
|---|---|
|
Materialization |
Performs the initial load of all data for a newly created virtual table. |
|
Regular refresh |
Executes scheduled refreshes based on the configured refresh interval. |
|
Manual refresh |
User-initiated refresh to capture older or corrected data outside the normal refresh window. |
|
Update |
Applies non-scheduled updates triggered by Change Broker to correct issues such as late or out-of-order data. |