← ZillizCONTENT HISTORY

Update to Zilliz

Snapshot Sep 30, 2026 · 23:15 UTC · version 1.4.4

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user wants to check the status of an async Cloud Job (backup, restore, migration, import, or clone). Also use when the user wants to wait for a long-running operation to complete.",
  "included_files": [],
  "name": "job",
  "skill_md_contents": "---\nname: job\ndescription: Use when the user wants to check the status of an async Cloud Job (backup, restore, migration, import, or clone). Also use when the user wants to wait for a long-running operation to complete.\n---\n\n## Prerequisites\n\n1. CLI installed and logged in (see setup skill).\n2. A job ID from a previous async operation (backup create, import start, etc.).\n\n## Commands Reference\n\n### Describe a Job\n\n```bash\nzilliz job describe --job-id <job-id>\n```\n\n## Wait for Completion\n\nThe `job describe` command supports a `--wait` flag to poll until the job finishes:\n\n```bash\n# Poll until done (default: 5s interval, 30min timeout)\nzilliz job describe --job-id <job-id> --wait\n\n# Custom timeout and interval\nzilliz job describe --job-id <job-id> --wait --timeout 600 --interval 10\n```\n\n## Job Types\n\n| Type             | Triggered By                                          |\n| ---------------- | ----------------------------------------------------- |\n| BACKUP           | `backup create`                                       |\n| RESTORE          | `backup restore-cluster`, `backup restore-collection` |\n| IMPORT           | `import start`                                        |\n| MIGRATION        | Cloud migration operations                            |\n| CLONE_COLLECTION | Collection clone operations                           |\n\n## Job Statuses\n\n| Status      | Meaning                           |\n| ----------- | --------------------------------- |\n| PENDING     | Job is queued                     |\n| IN_PROGRESS | Job is running                    |\n| SUCCESSFUL  | Job completed successfully        |\n| FAILED      | Job failed (check `reason` field) |\n| CANCELING   | Job is being cancelled            |\n| CANCELED    | Job was cancelled                 |\n\n## Guidance\n\n- Many control-plane operations are **asynchronous** and return a `jobId`. Suggest using `job describe` to track progress.\n- When a job fails, the `reason` field contains the error message. Display it to the user.\n- For long-running operations (cluster creation, data migration), suggest using `--wait` so the user doesn't have to poll manually.\n- The `--wait` flag shows a live progress spinner. Users can press Ctrl+C to stop waiting without cancelling the job itself.\n"
}

SHA-256 of public snapshot: 7db7ee14e00ba8cff10c5ac08f0a13a8f0d7405b99e0ee950f4d33bd8c68b06b