I am trying to build a sync mechanism between Salesforce and AWS using AWS AppFlow(Event based).

But as per salesforce doc, Change Data Capture Events are only retained for 72 hours: https://developer.salesforce.com/docs/atlas.en-us.240.0.api_streaming.meta/api_streaming/using_streaming_api_durability.htm

Is there any way we can tackle this somehow that the events are not lost if the problem is not acted before 72 hours?

  • Why would you need events to be retained more than 72 hours?
    – David Reed
    Commented Jan 15, 2023 at 17:53
  • Aside from the answer to David's question, hopefully by "build a sync mechanism" you mean configuring the out of the box integration rather than building your own.
    – identigral
    Commented Jan 15, 2023 at 18:56
  • @identigral Yeah, correct
    – ashwini571
    Commented Jan 16, 2023 at 7:16
  • @DavidReed I'm thinking of a scenario where lets's say for some reason AppFlow is suspended and is not fixed before 72 hours then we will lose the events during that period of time.
    – ashwini571
    Commented Jan 16, 2023 at 7:18
  • More or less answered in salesforce.stackexchange.com/questions/321807/… . A more complete answer is this: there are a myriad of failure points in a message-oriented solution. These solution trade-offs are first a business decision. For example, if truly needed a lack of durable subscription feature can be worked around by having multiple subscribers and then reconciling missing messages if one sub is down. Mulesoft can be another CDC sub out of the box.
    – identigral
    Commented Jan 16, 2023 at 17:23

1 Answer 1


Here's an Article regarding the Event Relay in Salesforce

In Addition to this, while creating Event Relay Config, add the parameter RelayOption with


This will make sure to pick the events that are in Event Bus for 72 hours. I've done this integration myself and let me know if you have any queries.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .