<span id="为周期增量导入触发一次全量刷新"></span>

# Trigger a full refresh for periodic incremental import

```{raw} html
<div class="mo-api-page-show-toc" aria-hidden="true"></div>
```

Perform one full refresh for an eligible Doris or MySQL periodic incremental import.

```text
POST https://api.moi.matrixorigin.cn/v5/task/run-full-refresh
```

<span id="调用前准备"></span>

## Before you call this API

Prepare a personal access token for the target workspace and the required source-read or import-run permissions. Install jq and set the example variables. See [common information](objects.md) for identity, environments, and result handoff.

<span id="请求体"></span>

## Request body

:::::::{div} mo-api-tabs
::::::{tab-set}
:::::{tab-item} Request example

```bash
curl -X POST "https://api.moi.matrixorigin.cn/v5/task/run-full-refresh" \
  -H "X-API-Key: $AI_STUDIO_API_KEY" \
  -H "X-Workspace-ID: $WORKSPACE_ID" \
  -H 'Content-Type: application/json' \
  --data-binary "$(jq -n --arg v0 "$TASK_ID" '{"task_id":$v0}')"
```

:::::
:::::{tab-item} Parameters

The task must be active, have created or uploading status (1 or 2), and use run_mode=periodic and sync_strategy=incremental. Sources are limited to Doris or MySQL without compute. Kafka, REST API, and ordinary file imports are unsupported. This execution overrides the sync strategy with full_refresh while retaining the periodic task and configuration. A successful response does not mean target data has finished refreshing. Confirm through run records, errors, and target data. Reread unknown outcomes before resubmitting.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `task_id` | string | Yes | Structured import task ID in the current workspace. |

:::::
::::::
:::::::

<span id="成功响应"></span>

## Successful response

:::::::{div} mo-api-tabs mo-api-response-tabs
::::::{tab-set}
:::::{tab-item} Response example

```json
{
  "code": "OK",
  "msg": "OK",
  "data": null
}
```

:::::
:::::{tab-item} Fields

| Field | Type | Description |
| --- | --- | --- |
| `code` | string | OK on success; also check the HTTP and business codes. |
| `msg` | string | Response information. |
| `data` | null | The request has been accepted; no execution result is returned here. |

:::::
::::::
:::::::

<span id="错误响应"></span>

## Error responses

Distinguish parameters, capabilities, authorization, and run states using [errors and environments](objects.md#errors-and-environments). HTTP 200 alone does not establish business success.
