A valid request URL is required to generate request examples[
{
"task_id": "<string>",
"job_history_id": "<string>",
"index": 123,
"query": "<string>",
"status": "<string>",
"details": "<string>",
"run_type": "<string>",
"start_position": "<string>",
"last_checkpoint": "<string>",
"records_inserted": 123,
"records_merged": 123,
"records_deleted": 123,
"error_message": "<string>",
"affected_rows": 123,
"runtime": "<string>",
"last_run_at": "2023-11-07T05:31:56Z",
"run_start_at": "2023-11-07T05:31:56Z",
"instance_id": "<string>",
"source_table": "<string>",
"destination_table": "<string>"
}
]{
"code": 123,
"message": "<string>",
"error": "<string>",
"error_code": "INVALID_REFERENCE",
"provider_id": "<string>",
"item_name": "<string>"
}{
"code": 123,
"message": "<string>",
"error": "<string>",
"error_code": "INVALID_REFERENCE",
"provider_id": "<string>",
"item_name": "<string>"
}List task statuses of a job
Not available for Load Folder jobs. For jobs using the new status table (statusversion >= 26.3), running task responses may populate affected_rows from the ReplicateEngine realtime status table. affected_rows is nullable: an unavailable count is null, including while running when a live count cannot be obtained. A known zero remains 0. Clients that previously checked for -1 must handle null instead; counts from an earlier independent job run are not used as a fallback. An automatic retry is another attempt of the same run, not a separate run. During RETRY RUNNING, the live total includes retained writes from an earlier partial-success attempt when the retry preserves them. Retries that drop, truncate, or refresh destination data use only the current attempt’s count. If the retained baseline or current live count is unavailable, the total is null. Per-operation live counts are also cumulative when both attempts report that metric, or null when a contribution is unknown. Completed tasks use the final task history value as the authoritative count without adding the baseline again. These counts are affected-row totals, not destination table sizes or counts of distinct records. Running task runtime is calculated from the current attempt’s start time when queried; temporary progress is not written back to task history.
A valid request URL is required to generate request examples[
{
"task_id": "<string>",
"job_history_id": "<string>",
"index": 123,
"query": "<string>",
"status": "<string>",
"details": "<string>",
"run_type": "<string>",
"start_position": "<string>",
"last_checkpoint": "<string>",
"records_inserted": 123,
"records_merged": 123,
"records_deleted": 123,
"error_message": "<string>",
"affected_rows": 123,
"runtime": "<string>",
"last_run_at": "2023-11-07T05:31:56Z",
"run_start_at": "2023-11-07T05:31:56Z",
"instance_id": "<string>",
"source_table": "<string>",
"destination_table": "<string>"
}
]{
"code": 123,
"message": "<string>",
"error": "<string>",
"error_code": "INVALID_REFERENCE",
"provider_id": "<string>",
"item_name": "<string>"
}{
"code": 123,
"message": "<string>",
"error": "<string>",
"error_code": "INVALID_REFERENCE",
"provider_id": "<string>",
"item_name": "<string>"
}Authorizations
A Sync user auth token. Generate one via POST /v2/users/generate-token.
Path Parameters
Job identifier.
Response
Task statuses
Job execution owning the effective task history; null when a matching history is not yet available.
The task run status, e.g. QUEUED, RUNNING, SUCCESS, RETRY SUCCESS, PARTIAL_SUCCESS, RETRY PARTIAL_SUCCESS, FAILED, RETRY FAILED, ERROR, or SKIPPED. PARTIAL_SUCCESS (and RETRY PARTIAL_SUCCESS) indicates that at least one chunk succeeded and at least one chunk failed; the task is retried when Automatic Retry is enabled.
A detailed message for the status. For failed or partial-success tasks this is the error message; for successful tasks it is a summary such as "Records affected: N". Returned as a flat string for backward compatibility.
Replication run type reported by ReplicateEngine for upgraded jobs (statusversion >= 26.3), e.g. FULL_SNAPSHOT, INCREMENTAL_SNAPSHOT, PARTITIONED_SNAPSHOT, INCREMENTAL, or CDC. Null when unavailable.
Position the run started from, such as a timestamp or CDC position. Null when unavailable.
Last checkpoint reached by the run. Null when unavailable.
Records inserted by the run, summed across automatic retries that keep previous writes. Null when unavailable.
Records merged by the run, summed across automatic retries that keep previous writes. Null when unavailable.
Records deleted by the run, summed across automatic retries that keep previous writes. Null when unavailable.
Error message of a failed or partially successful completed run. Null otherwise.
Records affected by the task, or null when the count is unavailable. A known zero is 0. Unknown counts are not represented by -1 or a count from an earlier independent job run. An automatic retry is another attempt of the same run. For upgraded jobs (statusversion >= 26.3), running tasks may return a realtime value from the ReplicateEngine status table. During RETRY RUNNING, the total includes retained writes from an earlier partial-success attempt when the retry preserves them. Retries that drop, truncate, or refresh destination data use only the current attempt's count. If the retained baseline or current live count is unavailable, the total is null. Completed tasks use the final task history value without adding the baseline again. This is an affected-row total, not the destination table size or a count of distinct records.
Elapsed time from the current attempt start while running; final stored runtime after completion.