Http Request activity is giving empty response with status 200

Help Robot
, , , ,
1

Hello Team,
Need help on Http Request activity.

I am calling API to create a service now ticket and getting a REQ#/ticket number from Dispatcher Robot.
Later when Performer Bot calling the API with Get method and getting status 200 based on Simple Authentication but with Empty response content, Whereas if I run the Dispatcher Bot’s Code via UiPath Studio the same API is giving answer…

Solutions tried till yet :

  1. Http Request activity’s timeout increased to 30sec
  2. Put Delay before and after API call
  3. Put Http Request activity in retry scope
    I have tried above possible solution but still unable to get the response…

Note : I am running Dispatcher & Performer in the same machine with same Bot Id and API authentication credential is also same.

2

@HAFIZUR_REHMAN_ANSARI

Welcome to the community

Can you please check what is the difference between the requests in dispatcher and performer

Cheers

3

Hello @Anil_G ,
In Dispatcher, I am using POST method and passing the parameters in body and in Performer I am using Get method to fetch the value like sys_id.

There is no issue with Dispatcher bot, Performer code is also working in Studio and getting expected output but giving empty response content while running via Orchestrator.

4

@HAFIZUR_REHMAN_ANSARI

Can you check the end point also try logging the output and the endpoint to check if they are proper

cheers

5

Hi,

You can try the post method / query in postman & see if you are able to get response.

Thanks

6

Thanks for your advise, I tried but found correct endpoint with empty response content along with status 200.

Still waiting for the solution to this problem.

7

@HAFIZUR_REHMAN_ANSARI

In postman is it giving the correct response?

Can you relicate

Cheers

8

Hello @Anil_G,
Thank you for your suggestion to check in POSTMAN, The issue has been resolved now…
When I tested the URLs in POSTMAN I found few special characters was getting concatenated when passing the arguments along with Orchestrator triggering…
I have fixed the issue in code and now its working fine in both Studio and Orchestrator runs.

Thanks

9

Thank you @Jayesh_678 for your suggestion to check in POSTMAN.

1 Like
10

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.