Search Jobs¶
Every analysis the platform performs runs as a job. The Search Jobs view lists these jobs, so that you can see what is currently running, what has completed, and where an analysis has encountered errors.
Select Search Jobs in the main navigation.
The table¶
| Column | Content |
|---|---|
| Name | The search terms the job was started for. |
| Status | The current state of the job. See below. |
| Job type | The kind of analysis. See below. |
| Created on | When the job was started. |
| Created by | The user who started the job, or the system for monitoring jobs. |
| Project | The project the job belongs to. The entry links to the project. |
| Actions | Cancel, View Logs, and Delete. |
Job types¶
| Type | Meaning |
|---|---|
| Discovery | Searches for new indicators for the search terms and stages them in the Discovery view. |
| Asset | Scans the confirmed scope and updates the Assets view. |
| Monitoring Discovery | The recurring equivalent of Discovery, started by the monitoring schedule. |
| Monitoring Asset | The recurring equivalent of Asset, started by the monitoring schedule. |
| Employee Lookup | Enriches employee records with additional data, started through Employee data enrichment in Intel → Employees. Consumes employee lookup quota from the company plan. |
A newly created project or a newly added search term typically produces a Discovery job followed by an Asset job.
Statuses¶
| Status | Meaning |
|---|---|
| Completed | The job finished and all results were written. |
| Completed (with errors) | The job finished, but individual targets could not be analysed. The results are usable but incomplete. |
| Canceled | The job was cancelled before it finished. |
| Failed | The job failed. Use View Logs, where available, to investigate the cause. |
A job that has not yet finished is shown as still in progress and can be cancelled from its action menu. The Status filter offers the values that currently occur in the list, so a state with no jobs in it is not offered.
Completed (with errors) is common and does not normally require action: unreachable hosts, timeouts, and rate limits on external sources all produce it. Where the same target fails repeatedly, use View Logs to determine the cause.
Actions on a job¶
Select the action menu at the end of the row.
| Action | Available when | Effect |
|---|---|---|
| Cancel | The job is running. | Stops the job. Results already written are retained. |
| View Logs | Log data exists for the job. | Opens the log of the job. |
| Delete | The status is Canceled, Completed, Failed, or Completed (with errors). | Removes the job entry from the list. Results are not affected. |
Actions that do not apply to the current state of a job are shown but cannot be selected.
Finding a specific job¶
The table supports the standard filters described in Working with the interface.
| Objective | Approach |
|---|---|
| All jobs of one project | Filter the Project column, or select the job count in the Search jobs column of the projects overview. |
| Failed jobs or jobs with errors | Filter Status on Failed and Completed (with errors). |
| Only recurring jobs | Filter Job type on Monitoring Discovery and Monitoring Asset. |
| The most recent activity | Sort by Created on in descending order. This is the default. |
Checking whether an analysis has finished
A project shows the indicator Updating data next to its name while an analysis is in progress, and the projects overview reports the number of running jobs in the Search jobs column. Use Search Jobs when you need to know which stage the analysis has reached, rather than merely whether it is still running.