Invalid uri, "escaped absolute path not valid" in Integration Hub Essentials course

kim-lindgren
Kilo Sage

Hi,

 

In my student instance, I am setting up a flow with a custom spoke containing two custom-made actions: Get Trivia Question and Get Trivia Answer. When I test the flow, I get the error: "Invalid uri 'https://scripting.service-now.com/api/x_snc_now_trivia/trivia/getAnswer?sys_id=f46a14fadb7b2300a7873...': escaped absolute path not valid". The ID in the URI is identical to the Question ID that was passed from Get Trivia Question to Get Trivia Answer. My instructors don't know what is wrong, but they say that the same problem has appeared in the past. Does anyone have an idea?

 

kimlindgren_0-1667385095172.png

 

2 ACCEPTED SOLUTIONS

MattiasJonsson
ServiceNow Employee
ServiceNow Employee

It might be you're running into an issue that manifests itself in the latest version of Chromium based browsers (Chrome, Edge etc). It adds an invisible character in some places.

Try doing the same operation in Safari or Firefox, that should resolve it if this is the issue you're running into.

 

If helpful or correct, please indicate so!

View solution in original post

Hello Kim,

I followed your instruction to clear hidden character at the end of the string by clicking back space both on the Base URL as well as Resource Path and it worked like a charm..

 

Thank you,

View solution in original post

9 REPLIES 9

I had the same pattern. Removing the hidden spaces (i.e., backspacing) from the Query Parameters fixed the second error (invalid query).

 

Thank you- it worked!

ANINDYA SUNDAR
Tera Contributor

@kim-lindgren 

 some invisible character is added in the particular string which one you are setting in URL.  Now you can do 

var val="string";

var url=val.replace(/[^a-zA-Z0-9 ]/g, ''); and use the url value to set into API endpoint. It is working in my case.

Mallikarjun Arj
Tera Contributor

Idea is informative.🤗

chrisboylan
Tera Contributor

I was having a similar issue.   I was passing this as part of the URL --active=true^assignment_group=d937d0d097dfbdd071c872e11153afc5^sys_class_name=incident.   Turned out the call did not like the = and ^ symbols.    Replaced that string with active%3Dtrue%5Eassignment_group%3Dd937d0d097dfbdd071c872e11153afc5%5Esys_class_name%3Dincident and it worked.