Deploying triggered email automation for our summer campaign and running into a frustrating deployment error. The email template uses a custom Apex class (CampaignEmailHelper) to dynamically populate recipient data based on lead scoring, but deployment to our cloud production org fails.
Error deploying EmailTemplate/Summer_Campaign_Welcome:
Apex class not found: CampaignEmailHelper
Component: emailTemplates/Summer_Campaign_Welcome.email
Our SFDX project has the Apex class in force-app/main/default/classes/ and the email template in force-app/main/default/email/. Both files are included in the Change Set. The Apex class compiles fine in the sandbox and has 87% test coverage. This is blocking our campaign automation launch scheduled for next week. Any ideas on getting the email template to recognize the Apex dependency during deployment?
Check if CampaignEmailHelper is marked as global or public. Email templates require the Apex class to have specific access modifiers to be referenced. Also verify the class name in your email template matches exactly - Salesforce is case-sensitive for class references in Visualforce email templates.
This looks like another Change Set sequencing problem. Email templates validate their Apex references immediately during deployment, but the Apex class might not be compiled yet in the target org. Try deploying the Apex class separately first using SFDX CLI, let it compile and run tests, then deploy the email template. Change Sets process components in parallel which causes these dependency failures.
Look at your package.xml ordering. Apex classes should be listed before EmailTemplate in the package.xml file. Also, make sure you’re not using --checkonly flag which skips Apex compilation. The class needs to fully compile in the target org before the email template can reference it. Run a full deployment with test execution to ensure the class is properly compiled.