Catalog source job statuses indicate whether a job is in progress and whether it completed successfully, finished with partial results, or failed.
The main distinction for completed jobs is the scope of errors encountered during the job run. When errors affect individual assets but don't prevent the job from continuing, the job finishes with partial results and publishes the metadata it extracted. Some errors prevent the job from running or completing. Such errors can result from infrastructure, authentication, or connectivity issues that block access to the metadata source. The job then stops and doesn't publish metadata to the catalog.
The following table describes the catalog source job statuses in Metadata Command Center:
Status
Description
Submitted or Queued
The job is scheduled and queued but has not started.
Running
The job is in progress and scanning metadata sources. The status updates when the job completes to reflect the final outcome.
Completed
All operations completed successfully without errors. Metadata extraction and catalog updates completed as expected. Some warnings might be present.
For example, a job scanned all tables in the database and published metadata to the catalog without encountering any issues.
Completed with Errors
The job finished and published metadata, but skipped some assets due to non-fatal errors. The result is partial, but the catalog contains usable metadata.
The following issues can cause a job to complete with errors:
- Missing permissions on some assets
- Unassigned or improperly configured connections
- Unsupported SQL statements in specific queries
- Parser failures on individual queries or worksheets
- Tableau conversion errors for specific worksheets
- Format inconsistencies in some metadata entries
For example, a job encounters an UnassignedConnectionException error because a connection was not properly assigned. The error causes the job to skip some assets that don't affect catalog usability.
Review the job log to identify skipped assets. The extracted metadata might be usable despite missing assets.
Failed
A critical error stopped the job. The job could not fully extract the metadata.
The following issues can cause a job to fail:
- Password expired or invalid credentials
- Connection to metadata source unavailable
- Secure Agent not running or unreachable
- Metadata Foundation services unavailable
- Resource exhaustion or unrecoverable catalog source errors
For example, the Secure Agent was not running, preventing connection to the source.
Fix the underlying issue and then re-run the job. The fix might include restarting the Secure Agent or updating credentials to restore connectivity.
Canceled
The job stops before completion, because an administrator stops it manually or the system stops it automatically. Partial results are incomplete or unreliable.
For example, an administrator stopped the job during system maintenance.
Skipped
The job did not run because preconditions, such as dependencies on prior job completions, were not met.
For example, a job configured to run only if a previous job succeeded was skipped because the previous job failed.
Note:
Job status terminology might vary between customer environments and versions. Verify the correct status names in your environment.
To troubleshoot issues, open the Job Details page and review the job logs.
For jobs with Completed with Errors status, look for ERROR entries, errorMsg fields, and component IDs such as UnassignedConnectionException or ScannerComponent to identify skipped assets. Decide whether the missing assets are critical enough to fix and re-run.
For jobs with Failed status, identify the root cause such as authentication, connectivity, or Secure Agent status. Fix the issue and re-run the job.
The same errors might occur across multiple job runs but have different final statuses. For example, one job status is Completed and another is Completed with Errors. In such cases, the Completed job logged warnings rather than errors, or the error logging changed between runs.