You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am testing salesforce source connector to see if it can re-run old messages incase there is some issue or api limitation error. I am on connector version 3.18.2 with config like
I was not sure which naming will work so i added all of those that i could find in different documentation. But none of these work. The logs always show Replay from -1
As a workaround i found that i can send it as a part of topic like
SF_TOPIC: "/data/Fan__ChangeEvent?replayId=4497&"
and that seem to do the trick.
Question:
Do you know if the next release will have this fixed? What is the current config name? How does the connector handle API limit exceeded scenario?
The text was updated successfully, but these errors were encountered:
We can add the option, but just for 4.4.1 release, since 4.4.0 is already on vote. My suggestion for the API limits is to throttle or to check the limits ahead of time.
Hi,
I am testing salesforce source connector to see if it can re-run old messages incase there is some issue or api limitation error. I am on connector version
3.18.2
with config likeI was not sure which naming will work so i added all of those that i could find in different documentation. But none of these work. The logs always show
Replay from -1
As a workaround i found that i can send it as a part of topic like
and that seem to do the trick.
Question:
Do you know if the next release will have this fixed? What is the current config name? How does the connector handle API limit exceeded scenario?
The text was updated successfully, but these errors were encountered: