SAP Knowledge Base Article - Public

2535466 - Retry In SF Boomi Connector

Symptom

  • Retry is only for GET request namely query request.
  • Retry max times: 5
  • Retry internal duration: 5 minutes

Environment

Boomi

Resolution

OData

Condition:

Retry happens for HTTP response code 405 and 5XX other than 500.

Query

  1. Just retry with failed request because basic authentication information is with every OData request.

SFAPI

Condition:

Retry happens for all except SFWebServiceFaultException. And there is one exception within SFWebServiceFaultException, namely invalid session.

When "Invalid SFAPI session" of SFWebServiceFaultException is thrown out, the connector will retry for query.

Login

  1. retry if not SFWebServiceFaultException

Query

  1. Relogin before retry if session is invalid.
  2. Retry SFAPI query.
  3. Go on with query more if retry successfully.

QueryMore

  1. Relogin before retry if session is invalid.
  2. Retry with SFAPI query with pagination parameters instead of retry with query more because query more can't keep on when session is invalid.
  3. Go on with query more with new query session id if retry successfully.

for example

Page size is 200, and query more is failed at page no 3, namely starting row is 401.

SFQL: select username from User

SFQL parameters: maxRows => 200 and startingRow => 401

  1. Relogin before retry if session is invalid.
  2. Execute "select username from User" with parameters mentioned above namely get no 3 page directly instead of "sfapi.queryMore(querySessionId)"
  3. Go on with query more with new query session id.

Keywords

Boomi connector re-try logic , Boomi platform , retry , Boomi process connector , odata , sfapi , query , querymore , KBA , odata , query , successfactors boomi connector , sfapi , retry , querymore , dell platform , boomi process connector , retry in sf boomi connector , LOD-SF-INT-BPI , Dell & Boomi Infrastructure , LOD-SF-INT , Integrations , How To

Product

SAP SuccessFactors HXM Core all versions