0

I have an Informatica integration workflow processing around 200 or 100 records each session for 10 sessions concurrently to REST API (Salesforce). It first authorizes using connected app details (client_id), client and gets token and use this token to post the data to the REST API. However, I get 400 bad request, authentication failure (means it may face error at authorization itself) when I run 10 sessions at a time. With single session it runs fine, so the issue is not with the code and 5 sessions run good but sometimes we receive timeout based commit point.

Is there any concurrent api requests limit that is causing this issue?

1 Answer 1

0

There is a concurrent API limit for long-running REST requests in SF as documented here.

Apart from this, I hope you are reusing the access token returned from oauth until that token is invalid, Because authenticating it again and again may hit Login Exceeded limit if the load is huge.

5
  • It is better to quote the documentation using text since it is then searchable. The limits you have copied/pasted have a caveat immediately above them; this applies to long running requests only. Please update the answer accordingly.
    – Phil W
    Jun 15, 2022 at 7:11
  • Correct, its only for 20 seconds and above. Jun 15, 2022 at 7:16
  • The integration service using 10 sessions always hits the login url for token and then in downstream uses this token along with body to post to end point URL. you mean this 10 concurrent hitting login URL is causing issue, but I came to know from SF person the concurrent limit is 25, so why we get error for 10 requests at a time.
    – Dyas
    Jun 15, 2022 at 7:47
  • if 10 request are sent at a time, assume it already reached 25 requests, the remaining requests will be in queue and gets failed?
    – Dyas
    Jun 15, 2022 at 9:24
  • All requests above the limit will fail. It wont get queued. Jun 15, 2022 at 9:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .