Just checking if others are experiencing any issues with the SFPE connector?
I've noted that it's not tracking the replayID.
So when it's down any event during that time is missed.
I'm not having this issue, but I am having problems with the listener. I can't get it to pick up when a single event is published, but once I send another (with the same exact payload, different replay Id), both get picked up (then I get an error in SF saying I'm trying to update two records with the same SFDC record Id, as the responses are sent back at the same time once processing is complete). #sfpe Dell Boomi
Aaaand all it took was unattaching the process from the atom and reattaching.
These sorts of bugs are EVERYWHERE in Boomi. I really wish their deployment functionality was more reliable.
Also, Derek, I've seen the replay Id in both the header and the payload of the incoming platform event. Are the fields not being added to the profile when you're importing the connection operation, or are they just coming in as null?
Yeah we've seen that unattach/reattach issue also.
I do see the replay Id in the event header. The issue is that the listener itself is not using this Id to pickup where it left off.
Which means we have to find a workaround to resend any events generated while the Listener was stopped.
Hi Derek Byrne/Nate Lee
I have a same problem that platform event connector operation is not picking up the events from Sales force based on reply id where it was left on last successful execution. As its been a while this discussion was started, If you guys are came across any solution, please share it here that would be really appreciated.
Thanks in advance.
We had to add a resubmit option to the Event logs in SFDC. This way any events that were missed could be submitted manually from SFDC.
Haven't had to use it much as the connector has been very stable over the last 4-5 months.
Retrieving data ...