Sanity dataset copy fails at 25% with no error message

I understand how frustrating it is when dataset copying fails without a clear error message! The issue you're experiencing where the copy fails at 25% progress is something that needs direct investigation by Sanity support, as it's likely related to your specific dataset or project configuration.

Here are some steps to help resolve this:

Immediate Troubleshooting Steps

1. Check the copy job status - You can list all dataset copy jobs to see if there's more detail:

   sanity dataset copy --list

2. Try the --attach flag - If you have a job ID from a previous attempt, you can attach to it to see more details:

   sanity dataset copy --attach <job-id>

3. Try without history - Large document histories can sometimes cause issues:

   sanity dataset copy testing development --skip-history

4. Update your CLI - Try upgrading to the latest version (your versions are quite old):

   npm install -g @sanity/cli@latest

Common Causes for Copy Failures

Based on the dataset copy documentation, failures can occur due to:

• Large datasets with complex document histories
• Asset download issues (the copy process includes copying all assets)
• Network timeouts during the operation
• Insufficient permissions on the target dataset

Contact Sanity Support

Since this is consistently failing at 25% regardless of which datasets you're copying, you'll need help from Sanity's support team. They can access server logs to see the actual error:

• Slack Community: Join the Sanity Community Slack and post in the #help channel
• Email Support: Reach out to support@sanity.io with your project ID and the datasets you're trying to copy
• Include details: Mention the CLI versions you've tried, the approximate size of your dataset, and that it consistently fails at 25%

The support team will be able to check backend logs and identify what's causing the failure at that specific point in the copy process.