Considerations for Notifications
Learn about the considerations for sending and viewing notifications, such as notification limits.
Required Editions
| Available in: Lightning Experience |
| Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| User Permissions Needed | |
|---|---|
| To view notification types: | View Setup and Configuration |
| To create and edit notification types: | Customize Application |
Sending Notifications
- You can create up to 500 custom notification types.
- Each notification can have up to 10,000 users as recipients after expanding any groups, queues, or teams. To have more recipients, you can add an action to the same process within Process Builder or to the same flow in Flow Builder.
-
An org can execute up to 10,000 notification actions per hour. When you exceed this limit, no more notifications are sent in that hour, and all unsent notifications are lost. Notification actions resume in the next hour.
For example, if your notification action processes are triggered 10,250 times between 4:00 and 4:59, Salesforce executes the first 10,000 of those actions. The remaining 250 notifications aren’t sent and are lost. Salesforce begins executing notification actions again at 5:00.
- When you send a custom notification from a
process, the Target ID for the notification is the record that started
the process. However, target records that don't have their own detail
page (for example, a case comment, which appears only in a Case
Comment related list) don't support direct navigation. Use Flow
Builder to send the notification from a flow and specify either a
different Target ID or Target Page Reference.
Tip For examples showing how to specify the target using JSON, see pageReference. - The title and body fields of custom desktop and mobile notifications support plain text only.
- Desktop notification titles have a maximum of 120 characters, and notification bodies have a maximum of 320 characters. Longer notification bodies are truncated with an ellipsis (…).
- The content of custom mobile push notifications depends on the Display full content push notifications setting. If full content push notifications aren’t enabled, only the notification title is sent.
- When you disable a delivery channel for a standard or custom notification type, you pause the delivery of a notification. However, a notification is still created and stored whenever an existing notification type is triggered. If you enable a delivery channel for an existing notification type, the stored notifications become visible in the notification tray for that delivery channel.
- Mobile in-app notifications require the Enable in-app notifications setting. Mobile push notifications depend on a user’s device-level and, if available, app-level push notification settings. Push notifications for the Salesforce mobile app require the Enable push notifications setting.
- If you created a custom notification type with a mobile delivery channel before Winter ’20, your notification is automatically delivered to the Salesforce mobile app. If you create a custom notification type with a mobile delivery channel in Winter ’20 or later, you must manually enable the Salesforce mobile app and any other supported apps in Notification Delivery Settings.
Viewing Notifications
- Recipients can view notifications received within the last 30 days.
Older notification records are automatically deleted.
- On desktop, a user can view notifications from the last 30 days in their notification tray. The tray shows 50 notifications at a time, ordered by the most recent notifications. The user can scroll to view older notifications within the last 30 days.
- In the Salesforce mobile app, a user can view notifications from the last 30 days in the app’s bell icon. The bell icon shows 20 notifications at a time, ordered by the most recent notifications. The user can swipe to view older notifications within the last 30 days.
- Each user’s notification tray holds a maximum of 10,000 notifications. If the notification tray exceeds 10,000 notifications, the user can’t receive new notifications. A user can’t manually delete notifications, so when the notification tray exceeds 7,500 notifications, a purge job truncates the tray to 5,000 notifications. This purge job runs up to one time per day. To avoid dropped notifications, we recommend that a user receives an average of fewer than 5,000 notifications per day.
- In the Salesforce mobile app:
- A push notification for an individual notification type depends on a user’s app-level Push Notification Settings. If the mobile channel is enabled for a notification type, but a user disables push notifications for that type, the user doesn’t receive a push notification.
- If you enable the mobile delivery channel for a notification type after you’ve disabled it, users’ Push Notification Settings for that type default to enabled.
- A desktop notification can be delivered in real time to up to 1,000 concurrently logged-in recipients. Additional concurrently logged-in recipients must refresh their Salesforce page to see their latest notifications. Recipients who aren't logged in see their notifications as expected upon login.
- Your org saves your most recent 1 million custom notifications for view in notification trays. Your org can save up to 1.2 million custom notifications, but it trims the amount to the most recent 1 million notifications when you reach the 1.2 million limit.
- A desktop notification’s timestamp matches the time zone of the recipient’s web browser. The timestamp doesn’t match the time zone setting of the recipient’s Salesforce user profile.
Did this article solve your issue?
Let us know so we can improve!
