Hi Rick, My understanding is that there is an issue accessing the replayId in camel, and not an issue with the -2 durability that is actually served. From the code, I think the replayId should be set here in 2.22.x:
https://github.com/apache/camel/blob/camel-2.22.x/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/SalesforceConsumer.java#L165 So, few things I would try: + getting the CamelSalesforceReplayId header value + updating to the last 2.22.x version 2.22.5 (note that this branch is EOL) + updating to 2.24.3 + debugging and see why the L165 is not called... Hope that help, Alex On Thu, Jan 23, 2020 at 3:49 AM Rick Matusiewicz < rick.matusiew...@ibotta.com> wrote: > Hello, > > I am attempting to use the camel-salesforce component to subscribe to a > Salesforce PushTopic. I am having a couple issues: > > 1) When I set the replayId = -2 , and when my route starts up there are no > existing messages coming in even though there are messages on the PushTopic > in the past 24 hrs. I also see this log line: > [main] INFO o.a.c.c.s.i.s.SubscriptionHelper - Set Replay extension to > replay from `-2` for channel `/topic/AccountUpsert` > > 2) I update a record in my org to trigger a PushTopic message. My camel > route picks up the message. However, I have not been able to access the > event object, which includes the replayId of the message. Durable Messaging > is an absolute must for our integration, and so we need the replayId. > > Camel version: 2.22.0 > Camel-salesforce version: 2.22.0 >
