Issue with userIdentifier in Multi-Call Setup – Works in call2, Fails in call3

[Leofrancis]

Hi All,

I’m encountering an issue with a multi-call setup for API integrations in my current project. My setup involves three calls as follows:

1. call1 – Retrieves employee data and provides an XRefCode which I need for further calls.

2. call2 – Loops over call1's data, using userIdentifier in the URL to retrieve additional employee details. This call works successfully.

3. call3 – Similarly loops over call1's data, aiming to use userIdentifier in the URL to fetch employee work assignments. However, in this call, using userIdentifier results in the following error: Error while getting User Import Response WebService call failed with responseStatusCode null

1. What I’ve Tried:

   • When I replace userIdentifier in call3 with XRefCode, the call completes without issues but i can't see any value in the customproperty. This suggests userIdentifier might not be resolving as expected in call3.
   • However, mapping XRefCode directly as userIdentifier in call1 is not preferred in my case.
   • I verified that userIdentifier works fine in call2, so the issue seems specific to call3.

Question:

Has anyone encountered a similar issue with userIdentifier in multi-call setups? Are there any known limitations or workarounds that allow userIdentifier to resolve consistently across all calls without directly mapping it in call1? Any insights or suggestions would be much appreciated!

call3

{
"name": "call3",
"connection": "userAuth",
"url": "https://URL/${userIdentifier}/WorkAssignments",
"httpMethod": "GET",
"httpHeaders": {
"Content-Type": "application/json",
"Authorization": "${access_token}"
},
"colsToPropsMap": {
"customproperty19": "Data[0].Position.Job.ShortName~#~char"
},
"userResponsePath": "Data"
}

[rushikeshvartak]

Please share the logs & configuration in text file for easier debugging. Additionally, provide the task ID, error details, or specific line numbers where the issues occur to help us review the relevant sections efficiently.



⚠️ Important: Do not upload attachments containing sensitive information, such as IP addresses, URLs, company/employee names, or email addresses. For more information, refer to the Saviynt PII Policy.