First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Environment Hub
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
What Are Beta Versions of Managed Packages?
Create a Beta Package for First-Generation Managed Packages
Create and Upload a First-Generation Managed Package
Publish Extensions to Managed Packages
View Package Details in First-Generation Managed Packages
Notifications for Package Errors
Set the Notification Email Address
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Notifications for Package Errors

Accurately track failed package installations, upgrades, and uninstallations in subscriber orgs with the Notifications for Package Errors feature. Proactively address issues with managed and unmanaged packages and provide support to subscribers so that they can successfully install and upgrade your apps.

You can choose to send a notification to an email address in your org when a subscriber’s attempt to install, upgrade, or uninstall a packaged app fails. To enable this feature, contact your Salesforce representative.

Errors can happen with these package operations:

  • Installation
  • Upgrade
  • Push upgrade
  • Uninstallation

When an installation fails, an email is sent to the specified address with the following details:

  • Reason for the failure
  • Subscriber org information
  • Metadata of the package that wasn’t installed properly
  • Who attempted to install the package
This example email is for a package installation that failed because the base package wasn’t installed before the subscriber tried to install an extension.