- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2025 05:24 AM - edited 04-11-2025 05:28 AM
Hi everyone,
I have a question related to App Certification and synchronous outbound REST API calls.
In my scoped application, I have a Business Rule that calls a function from a Script Include. Inside that Script Include, I am using synchronous outbound REST calls (execute()) — first to generate an access token, and then to make 3–4 more API calls in sequence using that token.
I understand that ServiceNow recommends using executeAsync() to avoid synchronous behavior for performance and scalability (as per the KB article).
However, in my case:
- The logic needs to run sequentially
- The API calls are dependent on each other
- This flow is triggered from a Business Rule and I am using async business rule already.
Given this requirement, can I mark this as "Won’t Fix" in the review comments during the Certification process and explain the reasoning (that async isn't suitable here due to functional dependencies)?
Would that be acceptable as long as I clearly document it in the review notes?
Thanks in advance for any clarification or guidance!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2025 09:56 AM
@HaridasP Ideally it shouldn't impact but we never now what's going in the reviewers mind when they are reviewing your application.
Also, please consider marking my responses helpful and accepted solution if they address your question.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2025 06:44 PM
@HaridasP Instead of making a synchronous call (execute()) you can use executeAsync() using Script Actions and events. Trigger an event with parameters (token value received from the API) when you receive the response of the fast call. Trigger another event with params and pass this info to another script action which will make the second API call.
Using this event and script action chaining you won't have to use a synchronous API call and your finding will be fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2025 08:49 PM
Thanks @Sandeep Rajput for your suggestion.
Just to confirm, if I continue with the current synchronous logic (due to script complexity), and add a "Won’t Fix" with proper justification, will it affect the app certification?
Appreciate your help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2025 11:55 PM
Thanks @Sandeep Rajput for your suggestion.
Just to confirm, if I continue with the current synchronous logic (due to script complexity), and add a "Won’t Fix" with proper justification, will it affect the app certification?
Appreciate your help!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2025 09:56 AM
@HaridasP Ideally it shouldn't impact but we never now what's going in the reviewers mind when they are reviewing your application.
Also, please consider marking my responses helpful and accepted solution if they address your question.