---
schema_version: "1"
id: 0b40ead16e04815cd79ab8208256bbf46b74a8130250cf9912a9f12c87b30099
title: Send Reminders After Waiting for One of Several Possible Events Example
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_ref_elements_wait_examples_parallel.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_wait_examples_parallel.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 97b6b9c18e72b94ff30a316c09366543d0df78f02661f83b51bdaaacdce4d661
description: Create a flow that sends reminders before an account renews or a contract ends.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Send Reminders After Waiting for One of Several Possible Events Example

Create a flow that sends reminders before an account renews or a contract ends.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr></tbody></table>

You're designing a flow that reminds account owners to follow up with their customers a week before either the account renews or the contract ends. The flow sends a reminder email for whichever date occurs first.

## Example

This flow already contains these populated variables. Before the flow runs the Wait element, it looks up and stores the contract's **ID**, its parent account's **ID** and **OwnerId**, and the account owner's **Email**.

- **{!accountId}** contains the ID for the account
- **{!contractId}** contains the ID for the contract
- **{!accountOwner}** contains the ID for the account's owner
- **{!ownerEmail}** contains the account owner's email address

![Screenshot of a sample flow that waits for an absolute alarm event](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/flow/flow_wait_parallel.png)

The Wait element defines two time-based resume events.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_tip.png)

Tip Every time-based resume event consists of a base time and an offset. For record-based time, the flow needs three pieces of information to determine the base time: the object, the date/time field, and the specific record. The offset for record-based time works the same as it does for flow-based time. The flow must know the unit (either Days or Hours) and the number of those units. For both of these events, the base time is offset by -7 days, because weeks isn’t an acceptable offset unit.

The base time for the first event ("Week before account renews") is the value of **Account.Renewal\_Date\_\_c** (1) on the record whose ID is stored in **{!accountId}** (2). The offset is -7 days (3).

![Screenshot of the first event's parameters](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/flow/flow_wait_parallel_overlay1.png)

The base time for the second event ("Week before contract expires") is the value of **Contract.EndDate** (4) on the record whose ID is stored in **{!contractId}** (5). The offset is -7 days (6).

![Screenshot of the second event's parameters](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/flow/flow_wait_parallel_overlay2.png)

You only want to send one follow-up reminder and the flow always waits for both events, so neither of these events need wait conditions. However, just in case something goes wrong, set a fault path. In this example, the fault path sends an email that contains the fault message to the user who created the flow.

#### See Also

- [Specific Time Resume Event](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_pause_events_time.htm&release=264.0.0&type=5 "Resume the paused flow when a specific time occurs.")
- [Wait for Conditions Element](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_wait_for_conditions.htm&release=264.0.0&type=5 "Resume a flow interview after specific conditions are met. Each wait configuration that you define in a flow has optional wait conditions. At run time, these conditions determine whether the flow waits for the associated resume event.")
- [Wait for Amount of Time Element](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_wait_for_amount_of_time.htm&release=264.0.0&type=5 "Resume a flow interview after a specific amount of time.")
- [Wait Until Date Element](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_wait_until_date.htm&release=264.0.0&type=5 "Resume a flow at a specific date and time.")