Multiple client errors in ATF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2025 02:03 AM
I am writing an ATF where I am searching for a published article from the ESC portal search option. It does return the knowledge article in the Search page but this page is giving out client errors.
The error is the same :
"[SEARCH API] SearchCheckpointService: Unable to post checkpoint, Invalid callback type: no thrown error' was detected on the page being tested. " but each time it comes with a new unique ID as a prefix.
Examples :
- #183801 [SEARCH API] SearchCheckpointService: Unable to post checkpoint, Invalid callback type: no thrown error' was detected on the page being tested. See failing Test Logs.
- #179021 [SEARCH API] SearchCheckpointService: Unable to post checkpoint, Invalid callback type: no thrown error' was detected on the page being tested
- #177272 [SEARCH API] SearchCheckpointService: Unable to post checkpoint, Invalid callback type: no thrown error' was detected on the page being tested.
Ignoring the client errors is not helping as each time there I ignore and rerun the test, it gives out the error with a new unique prefix as seen above.
Any help would be appreciated.
Thanks,
Vyshali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2025 01:11 AM
Hi, I had the same issue and got help from ServiceNow. Instead of adding the error to the ignored/warning list, create a server (not client) error yourself in the [sys_atf_whitelist] table with the following values:
Error message: [SEARCH API] SearchCheckpointService: Unable to post checkpoint, Callback name missing:
Report level: Ignored - Step & Test will report Success
Error location: Server
My test ran after I created this 🙂