Manage Consumption Threshold Alerts and Notifications

You can access the Consumption Threshold Alerts flow in a sandbox, but you can’t run it there. The flow fails because Digital Wallet invocable actions aren’t supported in sandbox environments.

Before you begin, be sure that the Default Workflow User isn’t set to the Integration User. You can verify the Default Workflow User in Process Automation Settings in Setup.

Note This flow uses two flow core actions: Compute Consumption and Create Consumption Alerts. The job of these invocable actions is to retrieve data for the flows. This process doesn’t consume Data Cloud credits. However, the flow does count toward flow limits.

When you activate the Consumption Threshold Alerts Flow, users with the System Administrator profile receive in-app and email notifications. By default, alerts are sent when their org exceeds 50%, 70%, 80%, 85%, 90%, 95%, and 100% of a consumption card’s purchased entitlement.

The default notification behavior differs based on the threshold reached. Alerts are only triggered for cards that have active entitlements. If a customer's contract expires, notifications are no longer sent.

• After an org consumes 50%, 70%, 80%, 85%, 90%, and 95% of a card's entitlement, System Admin users receive one notification. No more notifications are sent until the next threshold is reached. Example: An org reaches 50% usage. System admins receive an alert on the 50% threshold. The next notifications are sent when the 70% threshold is reached.
• After an org consumes 100% of a card's entitlement, System admins receive a daily email on the usage status. The account is then invoiced monthly in arrears at the applicable usage rate on the Order Form for any additional consumption.
• If more capacity or credits are purchased and a previous threshold is reached again, another notification is sent. Example: A consumption card for data storage entitlements is 82% consumed. A System admin is alerted about the 80% threshold being exceeded and decides to buy more storage. After the purchase, the card’s consumption goes down to 52%. As the org consumes more and reaches 80% again, users receive the email notifying 80% for a second time.