القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user reports that a Zilliz Cloud cluster or Milvus collection is unhealthy, slow, stuck, returning errors, hitting quotas, or otherwise misbehaving — or when they ask "what's wrong with...", "why is ... slow", "diagnose ...", "troubleshoot ...".
Zilliz Cloud onboarding and usage assistant. Helps users understand Zilliz Cloud, choose the right plan, estimate costs, write code, debug issues, and adopt new features like Functions, Volumes, and Global Clusters. Use this skill whenever the user asks about Zilliz Cloud — including plan selection, pricing, cost estimation, capacity planning, cluster configuration, SDK usage, schema design, search patterns, migration, troubleshooting, MCP server setup, Terraform, auto-scaling, metrics/alerts, backup/restore, or any "how do I do X with Zilliz Cloud" question. Also trigger when the user mentions keywords like: "Zilliz", "zilliz cloud", "vector database", "which plan", "serverless vs dedicated", "CU", "vCU", "Milvus cloud", "pymilvus", "collection", "embedding function", "hybrid search", "rerank", "BM25", "global cluster", "BYOC", "tiered storage", "volume", "data import", "MCP server", "partition key", or error messages from Zilliz Cloud.
Use when the user wants to create, list, describe, delete, export, or restore backups, or manage backup policies on Zilliz Cloud.
Use when the user wants to check usage, view invoices, or manage payment methods on Zilliz Cloud.
Use when the user wants to create, list, describe, delete, suspend, resume, or modify Zilliz Cloud clusters.
Use when the user wants to create, list, describe, drop, rename, load, release, or manage collections and collection aliases in Milvus.
| name | job |
| 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. |
zilliz job describe --job-id <job-id>
The job describe command supports a --wait flag to poll until the job finishes:
# Poll until done (default: 5s interval, 30min timeout)
zilliz job describe --job-id <job-id> --wait
# Custom timeout and interval
zilliz job describe --job-id <job-id> --wait --timeout 600 --interval 10
| Type | Triggered By |
|---|---|
| BACKUP | backup create |
| RESTORE | backup restore-cluster, backup restore-collection |
| IMPORT | import start |
| MIGRATION | Cloud migration operations |
| CLONE_COLLECTION | Collection clone operations |
| Status | Meaning |
|---|---|
| PENDING | Job is queued |
| IN_PROGRESS | Job is running |
| SUCCESSFUL | Job completed successfully |
| FAILED | Job failed (check reason field) |
| CANCELING | Job is being cancelled |
| CANCELED | Job was cancelled |
jobId. Suggest using job describe to track progress.reason field contains the error message. Display it to the user.--wait so the user doesn't have to poll manually.--wait flag shows a live progress spinner. Users can press Ctrl+C to stop waiting without cancelling the job itself.