https://community.dynatrace.com/t5/Troubleshooting/Troubleshoot-Multiple-selectors-were-not-found-errors-in/ta-p/298562 <H2>Summary</H2> <DIV> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"> <DIV>This article provides a structured troubleshooting workflow for resolving the Dynatrace Synthetic Clickpath errors&nbsp;<STRONG>Multiple selectors were not found</STRONG>&nbsp;and&nbsp;<STRONG>1502 – The HTML element could not be found to perform action.</STRONG>. It walks through how to identify the true failing Synthetic event, distinguish between locator and event‑trigger issues, and debug failures using screenshots, DevTools, and manual navigation. You’ll learn how to build resilient DOM or XPath locators, fix broken clickpaths without re‑recording, and reliably trigger custom JavaScript events when standard Synthetic actions aren’t sufficient. The goal is to create robust Synthetic browser monitors that withstand UI changes and reduce false failures.</DIV> </DIV> </DIV> <P>&nbsp;</P> <P><LI-TOC indent="15" liststyle="disc" maxheadinglevel="3"></LI-TOC></P> <P>&nbsp;</P> <DIV class="lia-message-template-content-zone"> <H2>Problem</H2> <DIV>The error <STRONG>Multiple selectors were not found</STRONG> in a Dynatrace Synthetic Clickpath means Dynatrace couldn’t uniquely identify an HTML element during playback. <DIV> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol">During scheduled or on-demand executions, this error appears as:&nbsp;<STRONG>1502 – The HTML element could not be found to perform action.</STRONG></DIV> </DIV> </DIV> <P>&nbsp;</P> <H2>Troubleshooting steps</H2> <H3>1 – Identify the real failing Synthetic event (Where)</H3> <DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">From the <STRONG>Monitor details</STRONG> page of the affected Synthetic browser monitor, select <STRONG>Analyze executions</STRONG> to open the <A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/analysis-and-alerting/multidimensional-analysis-for-browser-monitors" target="_self"><STRONG>Multidimensional analysis</STRONG></A> page.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Choose a single failed execution.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Locate the first step that deviates from the expected clickpath.</LI> </UL> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol">Ask yourself:</DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Is the flagged step the true root cause?</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Or did a previous step fail, leading to this error?</LI> </UL> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"><STRONG>Example</STRONG></DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Step “Click Go to XYZ” completes.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">The next step shows the same page instead of XYZ.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Root cause: The previous click step failed, not the one highlighted in red.</LI> </UL> <P>&nbsp;</P> </DIV> </DIV> <DIV class="lia-message-template-content-zone"> <H3>2 – Check if the element was selected (What)</H3> <DIV> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol">In the root cause step:</DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Review the <STRONG>Actual</STRONG> screenshot.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Check if the expected element is highlighted with a dotted box.</LI> </UL> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"><STRONG>Outcomes</STRONG></DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"><STRONG><span class="lia-unicode-emoji" title=":heavy_multiplication_x:">✖️</span> No highlighted element</STRONG> → Locator failed → Element not found.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"><STRONG><span class="lia-unicode-emoji" title=":white_heavy_check_mark:">✅</span> Element highlighted</STRONG> → Element found → Action likely didn’t trigger.</LI> </UL> <P>&nbsp;</P> </DIV> <H3>3 – Navigate to the failure context manually (Prepare a debugging context)</H3> <DIV> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol">To ensure accurate debugging, do one of the following:</DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"><STRONG><span class="lia-unicode-emoji" title=":play_button:">▶️</span> Playback clickpath</STRONG> and keep the clickpath recorder tab open after failure. <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">If the element isn't shown in the page where the clickpath fails, use Manual navigation.</LI> </UL> </LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"><STRONG><span class="lia-unicode-emoji" title=":globe_with_meridians:">🌐</span> Manually navigate</STRONG> through the monitored web app: <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Use the same steps as the clickpath.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">In a private browser window.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Reproduce the exact context before failure.<BR /><BR /></LI> </UL> </LI> </UL> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"><STRONG>Tip</STRONG>: Open <STRONG>DevTools (F12)</STRONG> at the start so all elements appear in the <STRONG>Elements</STRONG> tab. For playback, this can be done after the initial navigation is performed.</DIV> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol">&nbsp;</DIV> </DIV> <H3>4 – Get an element locator manually (JS Path)</H3> <UL> <LI>Right‑click the target element → Inspect</LI> <LI>Confirm the correct HTML node is selected:&nbsp; <UL> <LI>Hover over the highlighted HTML <UL> <LI>This should highlight the element in the rendered page</LI> </UL> </LI> <LI> <DIV>Repeat if needed to select correctly.</DIV> </LI> </UL> </LI> <LI> <DIV>Right-click the HTML node → <STRONG>Copy → Copy JS path</STRONG>.</DIV> </LI> </UL> <P><STRONG>Test the locator</STRONG></P> <UL> <LI>Paste into the Console: <PRE>document.querySelector("...")</PRE> </LI> <LI>Press Enter <UL> <LI>If the element is returned and highlights correctly → Locator is valid.</LI> <LI>If not, inspect parent or child nodes until correct element is found. <DIV>&nbsp;</DIV> </LI> </UL> </LI> </UL> <P><STRONG>Test the action</STRONG></P> <UL> <LI>Paste again in the Console call the method .click(). <PRE>document.querySelector("...").click();</PRE> </LI> <LI><span class="lia-unicode-emoji" title=":white_heavy_check_mark:">✅</span>&nbsp;<STRONG style="font-family: inherit;">Action occurs</STRONG><SPAN> → Locator is correct.</SPAN></LI> <LI><span class="lia-unicode-emoji" title=":cross_mark:">❌</span>&nbsp;<STRONG style="font-family: inherit;">Nothing happens</STRONG><SPAN> →</SPAN> <DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Event listener issue → See step 7.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Element in iframe, shadow DOM, or slot → Try XPath method.<BR /><A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/How-to-add-an-XPath-locator-in-a-Browser-Clickpath-Monitor/ta-p/214051" target="_blank" rel="noopener">How to add an XPath locator in a Browser Clickpath Monitor script</A></LI> </UL> </DIV> </LI> </UL> <P>&nbsp;</P> <DIV> <H3>5 – Move the verified locator into Dynatrace</H3> <UL> <LI>Edit the recorded clickpath step identified in step 1.</LI> <LI>Remove existing locators (usually CSS).</LI> <LI>Add one locator: <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"><STRONG>Type</STRONG>: DOM</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"><STRONG>Value</STRONG>: Verified JS path (without <CODE>.click()</CODE>).</LI> </UL> </LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Save and playback.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">If still failing → See step 6.</LI> </UL> <P>&nbsp;</P> </DIV> <DIV> <H3>6 – When the element is found but the action does not occur (How)</H3> <H4><STRONG>Scenario A – Triggered event ignored</STRONG></H4> <UL> <LI>Try trusted events →&nbsp;<A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/How-to-interact-with-trusted-events-in-a-Browser-Clickpath/ta-p/222074" target="_blank" rel="noopener">How to interact with trusted events in a Browser Clickpath Monitor</A></LI> </UL> <H4><STRONG>Scenario B – Wrong element selected</STRONG></H4> <UL> <LI><SPAN>Locator points to a visual element, not the one handling the event.</SPAN></LI> <LI> <P><STRONG>Fix</STRONG>: Refine locator to the element with the event listener (see step 7).</P> </LI> </UL> <P><STRONG>Scenario C – No matching listener exists</STRONG></P> <UL> <LI>The app uses different events than click or keystroke. Standard Synthetic actions won’t trigger them.</LI> <LI><STRONG>Fix:</STRONG> Dispatch programmatically the required event <UL> <LI><A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/How-to-perform-a-click-event-using-Javascript-on-browser/ta-p/244503" target="_blank" rel="noopener">How to perform a click event using Javascript on browser clickpath synthetic monitors</A></LI> <LI><A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/How-to-perform-a-right-click-in-a-Browser-Clickpath-Synthetic/ta-p/233062" target="_blank" rel="noopener">How to perform a right-click in a Browser Clickpath Synthetic Monitor</A></LI> <LI><A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/How-to-perform-Location-dropdown-auto-complete-Address-with-help/ta-p/209241" target="_blank" rel="noopener">How to trigger dropdown (auto complete) with help of JavaScript Event on browser click path synthetic monitor.</A></LI> </UL> </LI> </UL> <P>&nbsp;</P> <H3>7 – Verify event listeners</H3> <P>With the element selected in <A href="https://developer.chrome.com/docs/devtools/elements/" target="_blank" rel="noopener"><STRONG>Elements tab</STRONG></A>&nbsp;(like in section 4), check the <STRONG>"Event Listeners"&nbsp;</STRONG>panel.&nbsp;</P> <UL> <LI>Confirm the expected listener (e.g. <CODE>click</CODE>).</LI> <LI>If missing: <UL> <LI>Inspect ancestors and child elements successively in the HTML hierarchy</LI> <LI>Look for the element that's associated with the listener the Clickpath needs to trigger.</LI> </UL> </LI> <LI> <DIV>When correct element found, repeat step 4.</DIV> </LI> <LI>If no listener exists, the app likely expects a different event sequence.</LI> </UL> </DIV> <P style="margin: 0in; font-size: 10.5pt;" lang="de">&nbsp;</P> <H3>8 - Elements that resist selection</H3> <DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Some apps use <A href="https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_shadow_DOM" target="_self"><STRONG>shadow DOM</STRONG></A> or <CODE><A href="https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/slot" target="_self">&lt;slot&gt;</A></CODE>, making selection harder.</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">Try using the <STRONG>Full XPath</STRONG> instead of JS path.</LI> </UL> <P>See guide:&nbsp;<A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/How-to-add-an-XPath-locator-in-a-Browser-Clickpath-Monitor/ta-p/214051" target="_blank" rel="noopener">How to add an XPath locator in a Browser Clickpath Monitor script</A></P> </DIV> <P>&nbsp;</P> <H2>What's next</H2> <P><SPAN>If none of the previous steps resolved the issue, open a chat and provide a link to the monitor you're troubleshooting and the steps you've already completed.</SPAN></P> <H3>Related reading</H3> <A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Troubleshooting-Map/ta-p/250426" target="_blank" rel="noopener"><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp; Synthetic Troubleshooting Map</A></DIV> <DIV class="lia-message-template-content-zone"><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp; <A href="https://docs.dynatrace.com/docs/shortlink/id-brower-clickpath-events" target="_self">Browser Clickpath events</A>&nbsp;</DIV> <DIV class="lia-message-template-content-zone"><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp; (Synthetic app) <A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-on-grail/synthetic-app/create-configure-browser-monitors" target="_self">Configure Browser Monitors</A></DIV> <DIV class="lia-message-template-content-zone"><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp; (Classic) <A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/browser-monitors/configure-browser-monitors" target="_self">Configure Browser Monitors</A></DIV> Wed, 13 May 2026 11:53:18 GMT Valentín 2026-05-13T11:53:18Z https://community.dynatrace.com/t5/Troubleshooting/Troubleshoot-Multiple-selectors-were-not-found-errors-in/ta-p/298562 <P><LI-TOC indent="15" liststyle="disc" maxheadinglevel="2"></LI-TOC></P> <DIV class="lia-message-template-content-zone"> <P>*<EM>Use a table of contents for longer articles.&nbsp;</EM></P> <H1>Summary</H1> <P><EM>*This is a mandatory section.</EM></P> <P><EM>Short description of which part of the Dynatrace platform the article refers to and what kind of problem it will help resolve / task it will describe.</EM></P> <P>&nbsp;</P> <H1>Problem</H1> <P><EM>*This is a mandatory section.</EM></P> <P><EM>Provide a precise description of the problem / task to be described.</EM></P> <P>&nbsp;</P> <H1>Troubleshooting steps</H1> <P><EM>*This section can be omitted.</EM></P> <P>&nbsp;</P> <H1>Resolution</H1> <P><EM>*This section can be omitted for ticket‑creation articles.</EM></P> <H1>What's next</H1> <P><EM>*This is a mandatory section.</EM></P> </DIV> Wed, 13 May 2026 11:53:18 GMT https://community.dynatrace.com/t5/Troubleshooting/Troubleshoot-Multiple-selectors-were-not-found-errors-in/ta-p/298562 Valentín 2026-05-13T11:53:18Z https://community.dynatrace.com/t5/Troubleshooting/Troubleshoot-Multiple-selectors-were-not-found-errors-in/tac-p/299421#M1111 <P>Thank you!&nbsp;<img class="lia-deferred-image lia-image-emoji" src="https://community.dynatrace.com/html/@9BD876A77FEF3D5EF4BC972CF8A97CB1/images/emoticons/take_my_money.png" alt=":take_my_money:" title=":take_my_money:" /></P> Wed, 13 May 2026 13:19:29 GMT https://community.dynatrace.com/t5/Troubleshooting/Troubleshoot-Multiple-selectors-were-not-found-errors-in/tac-p/299421#M1111 AntonPineiro 2026-05-13T13:19:29Z