We have a job which calls an API and response is used to perform the required logic. Now the same API job is used by multiple other jobs. Some how the responses are interchanged due to which the main job is failing. Can you please suggest some solutions.
If I understand it correctly, you're calling an API with a "main/first call" which the response data must be used in the API calls, but this "main call" is failing and therefore the rest of the calls?
Suppose, an API is called by multiple jobs by passing different parameters. Now, A job called the API at 10:51 with ABC as parameter and Z job called the same API with XYZ as parameter at 10:51. API job while sending response to A job it send XYZ data as the response instead of ABC parameter response. We can see that thread mismatch has not happened however response got mixed. Due to which jobs got failed.
Where are you making your calls? Throught the REST connector? If so, are the "jobs" in the same app/script or do they run separately? Is the data being stored in variables? If so, did you check if you're not overwritting the variable or something like that?
It's very weird indeed, but it could be something with the API. I'm far from expert, but I do consume some APIs in our application. Depending on the API you'd have an user and key, maybe the API sees the cliente calling it as one, specially if you're in the same network or whatever.
Note that every variable will keep the last loaded value until the values changes or you clear it. If for some reason the routine failed to add the parameter to a variable, you'd probably be calling with old parameters if you're using the same variable name.
