Skip to main content
This document introduces how to retry review tasks via REST API. When a review task execution fails or needs to be reviewed again, you can retry the entire review task or retry a specific rule in the review task.
Review tasks support two retry methods:
  1. Retry entire review task: Re-execute all rules in the entire review task
  2. Retry a specific rule: Re-execute only a specific rule in the review task

Retry Entire Review Task

Re-execute the entire review task, which will re-review all rules in the task:
Request Parameters:
  • workspace_id (required): Workspace ID
  • task_id (required): Review task ID
Response Example:

Retry a Specific Rule in Review Task

Re-execute only a specific rule in the review task, suitable for cases where only a specific rule needs to be reviewed again:
Request Parameters:
  • workspace_id (required): Workspace ID
  • task_id (required): Review task ID
  • rule_id (required): Review rule ID
Response Example:

Parameter Description

Review Task ID (task_id)

The review task ID is the identifier of a created review task. You can obtain it through:

Review Rule ID (rule_id)

The review rule ID is the identifier of a specific rule in the review task. You can obtain it through:
  • Querying task results via the Get Review Result API, from the groups[].review_tasks[].rule_id field
  • Obtaining rule IDs from the rule repository via the Rule Management API
Example: Get Rule ID from Review Result
Python

Use Cases

Retry Entire Review Task

Suitable for the following scenarios:
  1. Review task execution failure: When the entire review task execution fails, you can retry the entire task
  2. After rule repository update: When rules in the rule repository are updated, you can retry the entire review task to apply the new rules
  3. After extraction result update: When the associated extraction task results are updated, you can retry the review task to re-review based on the new extraction results

Retry a Specific Rule

Suitable for the following scenarios:
  1. Single rule execution failure: When a specific rule execution fails, you can retry only that rule without affecting other rules
  2. After rule configuration adjustment: When a specific rule’s configuration is adjusted, you can retry only that rule
  3. Improve efficiency: When only a specific rule needs to be reviewed again, retrying a single rule is more efficient than retrying the entire task

Notes

  1. Asynchronous execution: Retry operations are executed asynchronously. After retrying, you need to query the review status via the Get Review Result API
  2. Task status: Ensure the review task exists and can be retried. Deleted tasks cannot be retried
  3. Rule status: When retrying a rule, ensure the rule ID is correct and belongs to the specified review task
  4. Retry frequency: It is recommended to control retry frequency to avoid excessive system load from frequent retries
  5. Result overwrite: Retrying will regenerate review results, and the original review results will be overwritten