Monitor Batch Jobs
The Batch Operations module provides visibility into submitted operational jobs and their processing status.
This allows administrators to:
- Track operational progress
- Review validation results
- Identify failures
- Export job data
- Monitor provider processing
[IMAGE PLACEHOLDER: Batch jobs overview]
View batch jobs
All submitted operations appear within the Batch Operations job list.
The job list may include:
- Job type
- Submission time
- Processing status
- Success counts
- Failure counts
- User information
[IMAGE PLACEHOLDER: Batch job list]
Batch job statuses
Depending on processing state, jobs may appear as:
Status | Description |
|---|---|
Pending | Waiting for processing |
Running | Currently being processed |
Completed | Processing completed successfully |
Partial Success | Some records completed, others failed |
Failed | Processing failed |
Processing times depend on provider responsiveness, job size, and operational complexity.
View job details
To review detailed batch job information:
- Open Batch Operations
- Select the required job
- Open the job details view
[IMAGE PLACEHOLDER: Batch job details]
Detailed information may include:
- Validation results
- Failed records
- Provider responses
- Processing timestamps
- Operational summaries
Review failed records
If a batch operation encounters errors, failed records can typically be reviewed individually.
Common failure causes include:
- Invalid identifiers
- Unsupported operations
- Provider validation failures
- Missing attributes
- Permission restrictions
[IMAGE PLACEHOLDER: Failed record details]
Correct failed records and re-run smaller validation batches before retrying large uploads.
Export batch job results
Batch job results can be exported for:
- Operational reporting
- Troubleshooting
- Customer communication
- Audit tracking
Supported export formats may include:
- CSV
- Excel
[IMAGE PLACEHOLDER: Export batch results]
Large-scale operational processing
Large jobs may:
- Process asynchronously
- Complete in stages
- Depend on provider-side execution
- Produce delayed synchronisation updates
Completion within the IoT.live Portal does not always mean the underlying provider operation has fully completed.
Operational best practices
For large-scale production changes:
- Validate datasets carefully
- Test on smaller device groups first
- Monitor provider synchronisation
- Export and retain operational results
- Review partial failures before continuing