7 synchronicity-labs

troubleshoot Skill

诊断并恢复 sync. labs(sync.so)中失败、卡住、被拒绝或报错的任务,并安全地继续执行且不会重复扣费。涵盖登录问题、工具缺失、输入被拒、计划/额度/并发限制、任务卡顿或缓慢、超时后响应丢失、配音服务报错和口型质量差等问题,并可向 sync. 团队反馈问题。适用于"我的口型同步失败了""为什么被拒绝""一直在处理中""收到 429 或 402""sync 工具不见了"等场景,或任何 sync. 错误信息。不适用于首次安装配置(setup)或编写集成代码。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

Troubleshoot sync. work

sync. labs | Troubleshooting guide

Finds out what actually happened, says it plainly, and resumes the work without starting a second paid job.

1. Gather the facts

Collect what's known before guessing: the tool or request that failed, the exact error text and code, and any generation, project, asset or job ID. Then read the current state:

  • A generation: generations_get with its id. Note status, error and errorCode.
  • No ID: generations_list with a small limit, to find it.
  • The account: account_get-context for plan limits and concurrency, account_get-usage for credits.

Never ask for the user's API key or password, and don't paste signed media links into anything public.

2. Find the cause

| What you see | What it means | What to do |
| --- | --- | --- |
| Sign-in error, or the sync. tools are missing | The MCP connection is signed out, or the client hasn't loaded it | Reconnect with references/connect.md. Signing in in a browser tab doesn't sign in the agent's connection. A tool that's missing here may only exist in another client, such as Studio tools in ChatGPT. |
| PENDING or PROCESSING for a while | Normal for long or busy jobs. Dubbing can take longer than plain lipsync. | Keep polling the same ID. Pending isn't failed, and a second create won't make it faster. |
| A timeout or lost response after a create | The job may or may not have started | Look for it with generations_list, or retry the identical request with the same idempotency key, which returns the original if it exists. For a jobs_create-many set, send the identical call again with the same set idempotencyKey and items. Never switch to a new key to "recover". |
| concurrency_limit_reached | The plan's limit on simultaneous jobs is reached | Wait error.retryAfterMs (or for a running job to finish), then retry the same request. More creates won't clear it. |
| insufficient_credits, free_tier_generations_exhausted, generation_plan_duration_exceeded, plan_feature_unavailable | A plan or balance limit | Quote the message and point to https://sync.so/billing/subscription. Don't retry, and don't switch accounts to get around it. |
| A 4xx about the input (format, resolution, face, length, speaker) | sync. refused the media or settings | Explain which input and why, and fix only that. Don't quietly change the model, speaker, language or trim. references/media-input.md has the input checklist. |
| import_in_progress | A social-link import is still running | Wait retryAfterMs, then repeat the identical call. |
| FAILED with a voice-provider error during dubbing | Often the user's own ElevenLabs key, if they connected one to sync. | Check that key's credits and validity. Removing it from sync. falls back to sync.'s own. |
| COMPLETED, but the lipsync looks wrong | Usually the source: a turned or covered face, several faces, music under the voice, low resolution | Go through the input checklist. If an older model was used, suggest sync-3. A new attempt is a new paid generation, so quote it first. |
| The result is there but the link or download failed | The output exists | Recover the link with generations_get. Don't generate again. |

Failed generations aren't charged.

3. Resume

Say what the cause was, what you did, and what happens next. Resume the original workflow from where it stopped, reusing the same project, assets and keys. Leave anything you couldn't confirm as unknown, and don't promise a finish time you can't back up.

4. Report it

If feedback_send is available and the problem was a confusing error, a bug, a missing capability or a workaround, send one report per problem after you've dealt with it. Use the matching kind, a short message with the exact error text and what would have helped, and the tool, errorCode and generationId or jobId when known. Leave out secrets, signed links, personal data and the user's media. The report doesn't retry or fix the job.

配合站内内容