Batch Jobs
Batch jobs are scheduled or on-demand background tasks that run on the xAssets server. They handle discovery loads, transformation processing, report generation, and other automated operations.
Viewing Batch Jobs
Navigate to Admin > Batch > Batch Jobs to see the list of recent and active batch jobs.
The batch job list shows:
| Column | Description |
|---|---|
| Start Date | When the job started |
| Transformation | The transformation or process being run |
| User Launched | The user or API key that initiated the job |
| Status | Current status: Running, Completed, Failed |
| Error | Error details if the job failed |
| Update | Progress information for long-running jobs |
| Last Updated | When the status was last updated |
Types of Batch Jobs
Discovery Loads
When discovery data arrives from collection servers, PCs, or cloud integrations, xAssets processes the data in a batch job. This includes:
- Loading discovered asset data into the database
- Running recognition rules to match discovered items to known products
- Updating hardware specifications and software inventories
Scheduled Transformations
Transformations configured with a schedule run as batch jobs at the specified times. Common scheduled transformations include:
- Nightly data imports from external systems
- Weekly compliance reports
- Monthly notification emails
- Periodic data cleanup operations
On-Demand Operations
Some operations launch batch jobs when triggered by a user:
- Running a discovery scan
- Calculating the software licensing position
- Executing a bulk update or bulk transfer
- Running month-end financial processing
Monitoring Batch Jobs
Check the batch job list regularly to ensure:
- Scheduled jobs are running at expected times
- No jobs are stuck in "Running" status for abnormally long periods
- Failed jobs are investigated and resolved
If a batch job fails, the Error column shows the error message. Click on the job to see full details including the transformation script that was running and any partial progress information.
Aborting a Running Job
To stop a long-running or stuck batch job:
- Navigate to Admin > Batch > Batch Jobs
- Select the running job
- Click Abort Selected Batch Jobs
The job will be terminated on the next processing cycle. Note that aborting a job may leave data in a partially processed state depending on what the transformation was doing.
Warning: If a batch job is stuck in "Running" status for an abnormally long time, check the server's event log and the xAssets Batch Service status in Windows Services. A stopped batch service can leave jobs in a perpetual "Running" state.
Related Articles
- Scheduled Transformations — configuring automatic batch job schedules
- Integration and Data Operations with Transformations — the transformation system that batch jobs execute
- Database in Read Only Mode — batch jobs cannot run when the database is read-only