Connector Improvement: No REST fallback for SFDC connector
AnsweredThe current SFDC connector will automatically fallback to REST API incremental ingestion when bulk load fails. The REST based ingestion can be very slow and hides the data ingestion failure from our team. Our request is to provide the ability to disable the REST fallback so we can hard fail and fix things from our end. We would like to purely rely on bulk ingestion.
-
Official comment
Hi Amit,
Sadie from the Product team here. Thanks for submitting this request. Can you provide a little more information about how this would be helpful for you? What actions would you take to fix things on your side in the event of a hard fail?
Best,
Sadie
-
Hi Sadie,
The hard fail will allow us to figure out adhoc processes/individuals that are hogging the API and take appropriate action. It will also allow us to ask Salesforce to increase our API limit if needed. The current fallback masks the problem and by the time we realize the issue the adhoc processes/individuals that are hogging the API are already gone, so its hard to debug issues. Additionally, we have some tight latency SLAs we want to monitor and the REST fallback does not satisfy our latency requirements.
Please sign in to leave a comment.
Comments
2 comments