read_history
Access job execution history to analyze performance, troubleshoot failures, and audit data movements for monitoring job health and SLA compliance.
Instructions
Access job execution history to analyze performance, troubleshoot failures, and audit data movements. If not authenticated with CData Sync, you will be prompted for credentials. Each history record shows when a job ran, its status, duration, and records affected. Use 'list' to browse history with filters/sorting. Note: Count action not supported by API - use 'list' and count results client-side. Essential for monitoring job health and SLA compliance.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | No | List history records. For counts, use 'list' with 'top' parameter and count results client-side. | list |
| filter | No | ⚠️ KNOWN ISSUE: OData filters currently fail due to API limitation. Use 'top' parameter and filter results client-side instead. Example: Use top=100 then filter by JobName manually. | |
| orderby | No | Sort order (e.g., 'RunStartDate desc' for most recent first) | |
| select | No | Properties to include (e.g., 'JobName,RunStartDate,Status,Runtime,RecordsAffected') | |
| top | No | Maximum records to return (useful for recent history and counting) | |
| skip | No | Records to skip for pagination | |
| workspaceId | No | Workspace ID to use for this operation. Overrides the default workspace. Use 'default' for the default workspace or a UUID for specific workspaces. |