Metadata deployments (change sets or package) show successful without error message but the expected components are not deployed

Metadata deployments (change sets or package) show successful without error message but the expected components are not deployed

Apex , AppExchange , Packaging , Metadata , User Interface , Eclipse IDE , Change Sets

Last updated 17 days ago ·Reference W-5276857 ·Reported By 25 users

Scheduled - Summer '20

Summary
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.

Repro
1. Upload a change set containing an Apex Class from a source org.

2. Attempt to deploy the change set in the target org.

Actual Result:
Deployment status will show success via setup's user interface however, components for change set or package are NOT deployed.

Expected Result:
Success status indicates success only. If failure then the status should reflect the appropriate error OR deploy metadata without rolling back transaction.

Workaround
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.

Updates
9/13/2018: The underlying error that causes the exception during the post deploy compilation is being tracked via the following Known Issue:

Reference: W-4968444
Errors caused by incorrectly mapped class members on package upgrade/install/uninstall/changeset.
https://success.salesforce.com/issues_view?id=a1p3A000000FmjCQAS

9/17/2018: The workaround steps have been updated to recommend providing a time window for Support to run the fix in customer orgs.

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP28 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS12 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS123 CS137 CS138 CS13 CS133 CS132 CS14 CS148 CS142 CS15 CS152 CS151 CS16 CS17 CS18 CS19 CS20 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS30 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS50 CS51 CS52 CS53 CS54 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS71 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS82 CS83 CS84 CS85 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS93 CS94 CS95 CS96 CS97 CS98 CS99 EU7 EU8 EU10 EU12 EU13 EU14 EU15 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA121 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA130 NA134 NA133 NA136 NA135 NA132 NA131 NA146 NA142 NA141 NA154 NA155 NA172 NA174 NA171 NA173 NA196 NA21 NA37 NA39 NA44 NA45 NA46 NA47 NA49 NA52 NA54 NA57 NA58 NA59 NA61 NA62 NA64 NA65 NA66 NA67 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA79 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7

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.