list_enrichment_jobs
¶
list_enrichment_jobs(
workspace_name: WorkspaceName,
*,
config_overrides: Optional[IoTSiteWiseClientConfig] = None,
dataset_id: Optional[ID] = None,
property_alias: Optional[AssetPropertyAlias] = None,
time_series_id: Optional[TimeSeriesId] = None,
status: Optional[EnrichmentJobStatus] = None,
job_type: Optional[JobType] = None,
start_date: Optional[datetime] = None,
end_date: Optional[datetime] = None,
max_results: Optional[MaxResults] = None,
next_token: Optional[NextToken] = None,
) -> ListEnrichmentJobsResponse
Lists enrichment jobs within a workspace with optional filtering and pagination. Results are ordered by createdAt timestamp descending (newest first).
Filtering
Combine filters to narrow results:
- datasetId: Filter by dataset
- propertyAlias OR timeSeriesId: Filter by time series (specify one, not both)
- status: Filter by job status (e.g., RUNNING to find active jobs)
- jobType: Filter by enrichment type (currently only EVENT_DETECTION)
- startDate and endDate: Filter by job creation time range
Important Constraints
- You must specify either propertyAlias OR timeSeriesId, but not both
- Attempting to specify both results in an InvalidRequestException
- Date filters use ISO 8601 format
- startDate is exclusive, endDate is inclusive
Pagination
The operation returns up to maxResults jobs per page (default 50). If more results exist, the response includes a nextToken. Submit this token in a subsequent request to retrieve the next page.
Common Use Cases
- Find all running jobs: Filter by status=RUNNING
- List recent jobs for a dataset: Filter by datasetId with optional date range
- Monitor jobs for a specific sensor: Filter by propertyAlias or timeSeriesId
- Track all event detection jobs: Filter by jobType=EVENT_DETECTION
Performance
Performance is optimal when filtering by supported fields (datasetId, propertyAlias, timeSeriesId, status, jobType).
Parameters:
-
workspace_name(WorkspaceName) –The name of the IoT SiteWise workspace to list enrichment jobs from.
-
dataset_id(Optional[ID], default:None) –Filter jobs by dataset ID. Returns only jobs analyzing data from the specified dataset.
-
property_alias(Optional[AssetPropertyAlias], default:None) –Filter by property alias (human-readable sensor name). Specify either propertyAlias or timeSeriesId, but not both. Returns only jobs analyzing the specified property alias.
-
time_series_id(Optional[TimeSeriesId], default:None) –Filter by time series ID (system identifier). Specify either timeSeriesId or propertyAlias, but not both. Returns only jobs analyzing the specified time series.
-
status(Optional[EnrichmentJobStatus], default:None) –Filter by job status. Returns only jobs in the specified status. Use RUNNING to find active jobs, or FAILED to identify jobs requiring attention.
-
job_type(Optional[JobType], default:None) –Filter by enrichment job type. Currently only EVENT_DETECTION is supported. Use this filter to future-proof queries when additional job types are added.
-
start_date(Optional[datetime], default:None) –The exclusive start of the date range for filtering jobs by creation time. Jobs created after this timestamp are included. Use ISO 8601 format (e.g., 2024-01-01T00:00:00Z).
-
end_date(Optional[datetime], default:None) –The inclusive end of the date range for filtering jobs by creation time. Jobs created on or before this timestamp are included. Use ISO 8601 format (e.g., 2024-01-31T23:59:59Z).
-
max_results(Optional[MaxResults], default:None) –Maximum number of jobs to return per page. Defaults to 50 if not specified. Use smaller values for faster responses, larger values to reduce API calls.
-
next_token(Optional[NextToken], default:None) –Pagination token from a previous ListEnrichmentJobs response. Include this token to retrieve the next page of results. Omit for the first request.
Raises:
-
AccessDeniedException–Access is denied.
-
ConflictingOperationException–Your request has conflicting operations. This can occur if you're trying to perform more than one operation on the same resource at the same time.
-
InternalFailureException–IoT SiteWise can't process your request right now. Try again later.
-
InvalidRequestException–The request isn't valid. This can occur if your request contains malformed JSON or unsupported characters. Check your request and try again.
-
LimitExceededException–You've reached the quota for a resource. For example, this can occur if you're trying to associate more than the allowed number of child assets or attempting to create more than the allowed number of properties for an asset model.
For more information, see Quotas in the IoT SiteWise User Guide.
-
ResourceNotFoundException–The requested resource can't be found.
-
ThrottlingException–Your request exceeded a rate limit. For example, you might have exceeded the number of IoT SiteWise assets that can be created per second, the allowed number of messages per second, and so on.
For more information, see Quotas in the IoT SiteWise User Guide.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_iotsitewise/_services/io_t_site_wise.py
8598 8599 8600 8601 8602 8603 8604 8605 8606 8607 8608 8609 8610 8611 8612 8613 8614 8615 8616 8617 8618 8619 8620 8621 8622 8623 8624 8625 8626 8627 8628 8629 8630 8631 8632 8633 8634 8635 8636 8637 8638 8639 8640 8641 8642 8643 8644 8645 8646 8647 8648 8649 8650 8651 8652 8653 8654 8655 8656 8657 8658 8659 8660 8661 8662 8663 8664 8665 8666 8667 8668 8669 8670 8671 8672 8673 8674 8675 8676 8677 8678 8679 8680 8681 8682 8683 8684 8685 8686 8687 8688 8689 | |