Read the component-level message in Deployment Status, not the top-level failure. It names the missing dependency, failing test or version problem. Production also needs at least 75% Apex code coverage across the whole org (Salesforce Help).
Clientell AI, the AI Salesforce admin, reads your org first and drafts each change. It asks before it changes anything in production. On the Platform, AI Salesforce deployments have approval and rollback. If you want the background first, read what a change set is.
Why does my change set fail validation or deployment?
The top-level message is vague. The detail is one click away. In the target org, open Setup, search for Deployment Status, and click View Details on the failed row. Change sets show a bit more detail there than other deployment methods do (Salesforce Developers blog, 21-06-2018).
Each line falls into one of four buckets: a missing dependency, a failing test or low coverage, a release mismatch, or a metadata rule such as a master-detail field.
Always validate before you deploy. In Inbound Change Sets, click Validate first, then Deploy. Validate checks the components without changing anything (Salesforce Help).
What do the most common change set errors mean?
Here are the errors that come up most, what each one means, and the fix. Messages are as Salesforce documents them. Your exact text may differ by release.
| Error or symptom | What it means | Fix |
|---|---|---|
In field: QuickAction - no QuickAction named NewTask found | The change set uses the standard global action NewTask. The target org does not have it, or you left it out. | Add the NewTask global action to the change set. If the source org does not list it, create a global action with that name first. (Salesforce Help, 24-05-2026) |
The field apiVersion can't be '62' (your number will differ) | The Flow or Apex class was built in a source org on a newer release, often a preview sandbox. The target does not know that API version. | Wait until both orgs run the same release, or lower the component's API version by one in the source and upload a new change set. (Salesforce Help, 26-01-2026) |
| Code coverage below 75% | Production checks coverage across the whole org, not only the classes in your change set. | Run Validate first. Add or fix Apex tests until the org-wide figure reaches 75%. (Salesforce Help) |
| A required master-detail field is missing | A custom object with a parent-child link went up without its master-detail field. | Add the master-detail field to the change set, even if you did not change its default. (Salesforce Help) |
| Deployment blocked by pending Apex jobs | Apex code has pending or running jobs. | Cancel the jobs and schedule them again after the deploy, or allow deployments with Apex jobs in Deployment Settings. (Salesforce Help) |
| Sharing model change fails | You cannot insert a custom object, update its sharingModel, and add an owner-based sharing rule in one deploy. | Deploy in three steps: the object, then the sharingModel, then the owner-based rule. (Salesforce Help) |
| A test passes in the sandbox but fails on deploy | The test depends on data or settings that only the sandbox has. One known case: records a test creates are not marked as viewed, so filters on LastViewedDate return nothing. | Make tests create their own data. Use the FOR VIEW clause before you filter on LastViewedDate. (Salesforce Help) |
Real admins hit the same walls. One asked why a summarized field worked in a sandbox but failed in production (Salesforce Stack Exchange). Another asked why a test passed on validation and failed on deployment (Salesforce Stack Exchange).
How do I fix each error and deploy again?
Use this loop. It works for every row in the table.
- In the target org, open Deployment Status and click View Details. Copy every component-level message, not only the first.
- Fix them in the source org. Add missing dependencies with the View/Add Dependencies button, then add anything it misses by hand. Approval process fields on standard objects are one known miss (Salesforce Help).
- Clone the change set, or make a new one. You cannot edit a change set after you upload it.
- Upload it to production.
- Click Validate on the inbound change set. Read the result.
- Repeat until validate passes, then click Deploy.
If a validation passed in the last 10 days and every test passed, Quick Deploy skips the tests on the real run. Any other deployment in between cancels the quick deploy, so validate again (Salesforce Help).
Some things deploy but do not behave the way you expect:
- Active flows deploy as inactive. Turn them on by hand. Only one flow version goes in a change set (Salesforce Help).
- Picklist values in the target that are not in your change set become inactive.
- If you deploy a profile and record type without the record type's page layout, the layout assignment is removed. Include every page layout for every record type you ship.
How do I check a change set before I upload it?
Run this list before every upload.
- Click View/Add Dependencies and add every item it suggests.
- Add each flow's linked components, such as the Apex, fields and record types it calls.
- Add the master-detail field for any parent-child object.
- Add all page layouts for each record type, plus the field permissions in your profiles.
- Check the API version of new flows and classes against the target org.
- Check that no Apex jobs are pending in production.
- Run the Apex tests in the sandbox with the same test level you will use in production.
Then validate in production before the deploy window, not during it. For profile questions, see profiles vs permission sets.
Is it possible to remove fields using change sets?
No. Change sets cannot delete or rename components. Delete the component in the target org's Setup, or run a deployment with a destructive changes manifest through the Metadata API or Salesforce CLI (Salesforce Help, Metadata API Developer Guide). To rename, delete the old component in the target and upload the new one.
A sharing change can count as a delete. Moving an org-wide default from Controlled by Parent to Public Read/Write is one example.
When should I stop using change sets?
Stop when the same errors keep coming back. These are the signs:
- You rebuild the same change set three times a week because of missing dependencies.
- You need deletes, and you do manual clean-up in production every time.
- Two people deploy at once, and nobody knows which version is live.
- You need a history of who shipped what, and Deployment Status does not give you enough.
Alternatives include the Salesforce CLI, source control with a pipeline, and DevOps tools. See change sets vs modern DevOps and the change sets alternative page for a fair comparison. Change sets still win on one thing: they are built in, free, and fine for a small, rare release.
How do I deploy to production safely?
Validate first, deploy only after you approve, and keep a way back. Clientell AI asks before it changes anything in production, and Platform deployments have approval and rollback. See security and privacy.
Try it in Clientell AI: "Check my change set against production without deploying, explain each failure in plain words, and list the missing dependencies I need to add." Start the 14-day trial, no card.
Not ready to try it? Run the free, read-only health check on your org. Clientell MCP is $249 a month and Clientell Platform is $500 a month. See pricing.
FAQ: common questions about Salesforce change set errors
Why does my change set fail validation or deployment?
Usually a missing dependency, a failing Apex test, or a release mismatch. The component message in Deployment Status says which.
What does "no QuickAction named NewTask found" mean?
The change set refers to the standard NewTask global action and the target org cannot find it. Add the action to the change set and upload again.
Can I edit a change set after I upload it?
No. Clone it, change the clone, and upload the new one.
What are the best alternatives to change sets for enterprise deployments?
The Salesforce CLI with source control and a pipeline, or a DevOps tool. Pick based on how often you ship and how many people deploy.
Sources
- Deploy change sets from sandbox to production, Salesforce Help
- Special Behavior in Deployments, Salesforce Help
- Deployment error 'no QuickAction named NewTask found', Salesforce Help, 24-05-2026
- Error when deploying a change set: the field apiVersion can't be set to an unsupported version, Salesforce Help, 26-01-2026
- Components Available in Change Sets, Salesforce Help
- Deleting Components from an Organization, Metadata API Developer Guide
- Let's talk deployment, Salesforce Developers blog, 21-06-2018
Last updated: October 9, 2026
