重试索引任务

以同一个任务 ID 重新启动 run_state 为 failed 或 canceled 的索引任务，并返回更新后的任务。之后用同一个 ID 轮询获取索引任务。

任务进入 published 后，如需再次索引该文档，使用重新索引文档。重新索引流程详见重新索引并跟踪索引进度。

处于 run_state: superseded 的尝试无法重试，即使其 stage 为 canceled。如果你从某次重新索引的响应中保存了更新的任务 ID，轮询该任务。

1 min read

post/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry

Request example

curl --request POST \
  --url https://api.dify.ai/v1/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry \
  --header 'Authorization: Bearer <token>'

import requests

url = "https://api.dify.ai/v1/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry"
headers = {
    "Authorization": "Bearer <token>",
}

response = requests.request("POST", url, headers=headers)

print(response.text)

const response = await fetch('https://api.dify.ai/v1/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer <token>'
  }
});

const data = await response.json();
console.log(data);

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => 'https://api.dify.ai/v1/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry',
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_CUSTOMREQUEST => 'POST',
  CURLOPT_HTTPHEADER => [
    'Authorization: Bearer <token>',
  ],
]);

$response = curl_exec($curl);
curl_close($curl);

echo $response;

package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	url := "https://api.dify.ai/v1/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry"

	req, _ := http.NewRequest("POST", url, nil)
	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)
	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))
}

HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("https://api.dify.ai/v1/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry"))
    .header("Authorization", "Bearer <token>")
    .method("POST", HttpRequest.BodyPublishers.noBody())
    .build();

HttpResponse<String> response = HttpClient.newHttpClient()
    .send(request, HttpResponse.BodyHandlers.ofString());

System.out.println(response.body());

require 'uri'
require 'net/http'

url = URI('https://api.dify.ai/v1/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry')

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = url.scheme == 'https'

request = Net::HTTP::Post.new(url)
request['Authorization'] = 'Bearer <token>'

response = http.request(request)
puts response.read_body

Response

{
  "base_head_revision": 1,
  "candidate_fingerprint": null,
  "candidate_publication_id": null,
  "completed_at": null,
  "created_at": 1788681600000,
  "document_asset_id": "6ec0bd7f-11c0-43da-975e-2a8ad9ebae0b",
  "error": null,
  "execution_attempts": 0,
  "failure": null,
  "id": "e4a1f0b2-7c3d-4e5f-9a1b-2c3d4e5f6a7b",
  "knowledge_space_id": "9b2e5b7a-3c1d-4e2f-8a9b-1c2d3e4f5a6b",
  "max_execution_attempts": 3,
  "run_state": "dispatch_pending",
  "stage": "outline_built",
  "updated_at": 1788681800000,
  "version": 1
}

{
  "code": "knowledge_fs_invalid_request",
  "message": "Agent Knowledge Base request is invalid.",
  "status": 400
}

{
  "code": "knowledge_fs_invalid_credential",
  "message": "Invalid Agent Knowledge Base service credential.",
  "status": 401
}

{
  "code": "unauthorized",
  "message": "Access token is invalid",
  "status": 401
}

{
  "code": "forbidden",
  "message": "Sorry, you have reached the knowledge base request rate limit of your subscription.",
  "status": 403
}

{
  "code": "knowledge_fs_access_denied",
  "message": "Agent Knowledge Base operation is not allowed.",
  "status": 403
}

{
  "code": "knowledge_fs_access_denied",
  "failure": {
    "action": "contact_admin",
    "category": "authorization",
    "code": "KNOWLEDGE_FS_ACCESS_DENIED",
    "message": "You do not have permission to perform this Agent Knowledge Base operation.",
    "retryPolicy": "never",
    "traceId": "8f3a2c14-9d6b-4c07-b5a1-2e7d0c93f5b2"
  },
  "message": "You do not have permission to perform this Agent Knowledge Base operation.",
  "status": 403
}

{
  "code": "knowledge_fs_resource_not_found",
  "failure": {
    "category": "not_found",
    "code": "KNOWLEDGE_FS_NOT_FOUND",
    "message": "The requested Agent Knowledge Base resource was not found.",
    "retryPolicy": "never",
    "traceId": "8f3a2c14-9d6b-4c07-b5a1-2e7d0c93f5b2"
  },
  "message": "The requested Agent Knowledge Base resource was not found.",
  "status": 404
}

{
  "code": "not_found",
  "message": "The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.",
  "status": 404
}

{
  "code": "knowledge_fs_conflict",
  "failure": {
    "action": "configure_model",
    "category": "configuration",
    "code": "DOCUMENT_COMPILATION_PROFILE_CHANGED",
    "message": "The model configuration changed or is unavailable. Check the knowledge space models before retrying document processing.",
    "retryPolicy": "after_configuration",
    "traceId": "5e2a9c17-3b4d-4f60-8a1b-2c3d4e5f6a7b"
  },
  "message": "The model configuration changed or is unavailable. Check the knowledge space models before retrying document processing.",
  "status": 409
}

{
  "code": "knowledge_fs_conflict",
  "failure": {
    "action": "retry",
    "category": "conflict",
    "code": "KNOWLEDGE_FS_CONFLICT",
    "message": "The Agent Knowledge Base operation conflicts with the current resource state.",
    "retryPolicy": "manual",
    "traceId": "8f3a2c14-9d6b-4c07-b5a1-2e7d0c93f5b2"
  },
  "message": "The Agent Knowledge Base operation conflicts with the current resource state.",
  "status": 409
}

{
  "code": "knowledge_fs_request_too_large",
  "failure": {
    "action": "retry",
    "category": "configuration",
    "code": "VECTOR_SPACE_QUOTA_EXCEEDED",
    "message": "The workspace vector storage limit has been reached. Delete documents or upgrade the plan before indexing more.",
    "retryPolicy": "manual",
    "traceId": "5e2a9c17-3b4d-4f60-8a1b-2c3d4e5f6a7b"
  },
  "message": "The workspace vector storage limit has been reached. Delete documents or upgrade the plan before indexing more.",
  "status": 413
}

{
  "code": "knowledge_fs_upstream_unavailable",
  "message": "Agent Knowledge Base is unavailable.",
  "status": 502
}

{
  "code": "knowledge_fs_operation_unavailable",
  "message": "Agent Knowledge Base operation is not available.",
  "status": 503
}

{
  "code": "knowledge_fs_operation_unavailable",
  "failure": {
    "action": "retry",
    "category": "dependency",
    "code": "KNOWLEDGE_FS_UNAVAILABLE",
    "message": "A service required by Agent Knowledge Base is temporarily unavailable.",
    "retryPolicy": "manual",
    "traceId": "5e2a9c17-3b4d-4f60-8a1b-2c3d4e5f6a7b"
  },
  "message": "A service required by Agent Knowledge Base is temporarily unavailable.",
  "status": 503
}

post/knowledge-fs/spaces/{knowledge_base_id}/jobs/{task_id}/retry

Authorization

Authorizationstringheaderrequired#

每个请求都通过 API Key 认证：Authorization: Bearer {API_KEY}。应用接口使用应用 API Key，知识库接口使用知识库 API Key（快速开始）。

API Key 应保存在服务端，切勿嵌入客户端代码。缺失或无效的 Key 会返回 HTTP 401（unauthorized）。

Path parameters

knowledge_base_idstringrequired#

知识库 ID：即知识库 API 访问 对话框中所示服务 API 端点的最后一段（…/knowledge-fs/spaces/<knowledge base ID>），也是地址栏中 /datasets/new/ 之后的那一段。

task_idstringrequired#

索引任务 ID，以下各处出现的都是同一个值：重新索引文档响应中 queued 条目的 compilation_job.id、获取文档返回的 latest_task.id、获取文档的索引任务列表返回的 id，以及获取后台任务列表中 document 任务的 id。

Responses

application/json

重新启动的任务。run_state 为 dispatch_pending，error 和 completed_at 均为 null。

base_head_revisioninteger#

内部字段，跟踪任务时无需使用。

candidate_fingerprintstring#

内部字段，跟踪任务时无需使用。

candidate_publication_idstring#

内部字段，跟踪任务时无需使用。

completed_atnumber#

任务进入终态阶段的时间，Unix 纪元毫秒。运行期间及重试后为 null。

created_atnumber#

任务创建时间，Unix 纪元毫秒。

document_asset_idstring#

正在索引的文档文件 ID，可用于获取文档文件。该值为发起此任务的重新索引文档请求项中的 asset.id，即使你提交的是文档 ID 也是如此。

errorstring#

简短的失败消息，可能与 failure.message 不同。仅当 stage 或 run_state 为 failed 时设置，其他情况下为 null，已取消的任务也是如此。

execution_attemptsinteger#

已执行的尝试次数。重试索引任务会将其重置为 0，因此反复重试本身不会耗尽尝试次数上限。

failureobject#

任务失败时的错误详情，否则为 null。

Show child attributes

actionstring#

建议的下一步操作（如有）：configure_model、configure_parser、configure_source、contact_admin、reupload 或 retry。不适用时为 null。HTTP 错误响应体中不包含此字段。

categorystring#

失败类别：authorization、canceled、configuration、conflict、dependency、internal、not_found、rate_limit、timeout 或 validation。

codestring#

稳定的错误码，采用大写蛇形命名，例如 KNOWLEDGE_FS_CONFLICT 或 SOURCE_CREDENTIAL_TEST_FAILED。

messagestring#

错误码或失败类别对应的公开消息。不会暴露提供商的错误详情。

parametersobject#

描述失败细节的值，最多 8 个，键取自 attempt、currentRowVersion、documentCount、expectedRowVersion、fileSizeBytes、limit、maxFileSizeBytes、maxItems、modelType、providerKind、retryAfterSeconds 和 status。没有时为 null。HTTP 错误响应体中不包含此字段。

retryPolicystring#

重试是否有用：automatic（服务会自动重试）、manual（需自行重试）、after_configuration（先在 Dify 中修正知识库配置）或 never（需修改请求）。

stagestring#

失败所在的阶段，例如 query_generation 或 credential-test。不适用时为 null。HTTP 错误响应体中不包含此字段。

traceIdstring#

联系管理员时需提供的参考编号。在包含失败详情的成功响应中可能为 null，在 HTTP 错误响应体中可能不出现。

idstring#

索引任务 ID。

knowledge_space_idstring#

知识库的内部 ID，并非路径中的知识库 ID。

max_execution_attemptsinteger#

任务判定为失败前允许的尝试次数。

run_statestring#

当前尝试的调度状态：

dispatch_pending：已受理，等待分派给工作进程。
queued：已分派，等待工作进程处理。
running：工作进程正在执行任务。
retry_wait：已安排自动重试，stage 保持不变。
succeeded：与 stage: published 同时出现。
failed、canceled：终态。
superseded：较新的一次尝试取代了本次尝试。属于终态，此时报告的阶段为 stage: canceled，取消和重试操作都不接受此状态的任务。

未设置时为 null。重试索引任务会将其设为 dispatch_pending。

stagestring#

索引阶段，按推进顺序：

queued
parsed
outline_built
nodes_generated
projection_built
smoke_eval_passed
published

published 表示新修订版本已生效。failed 和 canceled 是另外两个终态值。重试索引任务会保留该次尝试已到达的检查点，因此重试后该值很少为 queued。

updated_atnumber#

任务最后变更时间，Unix 纪元毫秒。

versioninteger#

正在索引的文档文件的版本。

取消索引任务获取批量任务