ATF(SOW)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi my Friend
I’ve seen this exact behavior in SOW/Workspace ATF runs. The reason Ignore all errors doesn’t help is because this is a real client-side exception that keeps firing so ATF continues to catch it every time the page renders.
From your screenshot the error is:
#99800 [SEARCH EVAM] ResultTemplateMapper: No composite data found for evamDefinitionId: undefined
That points to a Workspace Search / Result Template configuration issue, where the Search component is trying to load EVAM (Experience Analytics) data but the EVAM definition id is blank/undefined.
What to do
Reproduce outside ATF
Open the same SOW page manually and check the browser console (F12).
If you see the same message, it confirms it’s not an ATF setting problem.
Fix the Search component config (the most common)
In UI Builder for that workspace, locate the page used in the failing step and find the Search / Results component.
Check the “result template / definition / analytics (EVAM)” related settings.
One of those is missing and is causing evamDefinitionId to be undefined.
If you don’t need analytics, disable EVAM for Search
If Experience Analytics is enabled for Workspace Search but not configured, turn it off for that experience/search.
This usually stops the ResultTemplateMapper error immediately and makes the test stable.
Why your test keeps failing
ATF can’t “ignore” an error that is thrown repeatedly during load; it will continue to detect it and mark the step as failed.
If you tell me which SOW page your ATF step is clicking into and which search component it uses, I can point you to the exact place in UI Builder where the EVAM/definition setting needs to be corrected or disabled.
@kishorek9987311 - Please mark Accepted Solution and Thumbs Up if you found Helpful!!
