git.repositories.retry-import

Start a failed import again from the same source

POST /git/api/repositories/{repoId}/import/retryIAM git:UpdateRepositoryChanges stateDestructive

Answers 202. A mirror reuses the token it keeps; a private source needs `token`.

Request syntax

POST /git/api/repositories/{repoId}/import/retry
{
  "token": "string"
}

Path parameters

  • repoIdRequired

    string

    Constraints: uuid

Request body

  • tokenOptional

    string

    A token for a private source; a mirror reuses the one it keeps

    Constraints: 1-1000 chars

Response

202 without `data`; the import is queued again and `get-import` follows it. 409 unless the import failed.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Fields of data

    Checked against the handlers: every route test validates their answers against this schema.

    Errors

    • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
    • 401No credentials, or an access key that is unknown, revoked or expired.
    • 403The caller's policies do not allow git:UpdateRepository on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
    • 404The resource does not exist in your organization.

    Examples

    The required parameters only, with example values. Replace id and the other placeholders with your own.

    dcloud git repositories retry-import repoId

    Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_repositories_retry-import.