- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2022 03:36 AM
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?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2022 03:49 AM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2022 01:42 PM
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,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2022 09:43 AM
I had the same pattern. Removing the hidden spaces (i.e., backspacing) from the Query Parameters fixed the second error (invalid query).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2024 10:59 AM
Thank you- it worked!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2022 10:36 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2022 10:43 PM
Idea is informative.🤗
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 12:02 PM
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.