Metadata deployments (change sets or package) show successful without error message but the expected components are not deployed
Last updated 10 days ago ·Reference W-5276857 ·Reported By 24 users
Metadata deployments via change sets or packages may show that the deployment was successful without any error messages.
However, upon checking - the expected components are not actually deployed or present in the target org.
This may occur if your change set contains Apex and requires the deploy to run tests.
When deployment is committed with tests, there is an Apex post deploy compilation that occurs. If this process encounters an exception the deployment may silently fail and rollback the metadata changes without notice and despite the user interface indicating that the deployment was successful without any errors.
1. Upload a change set containing an Apex Class from a source org.
2. Attempt to deploy the change set in the target org.
Deployment status will show success via setup's user interface however, components for change set or package are NOT deployed.
Success status indicates success only. If failure then the status should reflect the appropriate error OR deploy metadata without rolling back transaction.
Please contact Support via a new case with reference to this Known Issue and internal article #000348983 to confirm whether your org may be impacted.
In your case please include a System Administrator's documented permission for Support to:
1. Run the fix or scrutiny to remove all Apex Class Identifiers from org. There is no adverse impact and this allows for a clean Apex recompilation.
Impact to customers should be minimal and we will not be touching any actual data and only internally used class identifiers. The impact will be momentary slowness as we invalidate the cache, run clean-up, and then recompile all the apex classes. Please provide a scheduled downtime for Support if needed or this may be done after hours if specified.
2. After Support has verified the scrutiny was successful, customer's will need to recompile all classes on org or provide login access and permission for Support to do so.
9/13/2018: The underlying error that causes the exception during the post deploy compilation is being tracked via the following Known Issue:
Errors caused by incorrectly mapped class members on package upgrade/install/uninstall/changeset.
9/17/2018: The workaround steps have been updated to recommend providing a time window for Support to run the fix in customer orgs.
Reported By (24)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.