Applications Systems

WPM Transaction Step failed: No element was clicked.

Step failed, no element was clicked error message when assigning out a transaction. Transaction is unknown. Transaction is down. Transaction will not work. Recording works in player but not on the player. Web Performance Monitor transaction is not working (WPM). Error received on Transaction. Step Failed: No element was clicked. Link not clicked, image not clicked. Element not found, can't click link. Cannot click the link to proceed, Transaction is down, Transaction failing, Transaction fails.

First published date

12/13/2019 7:57 PM

Last published date

3/31/2023 6:09 AM

Overview

Transaction is failing due to 'No element was clicked'. This is often found on Transactions where the Recording may work as expected, but once assigned to the Player, it fails. 

This is known to fail both consistently and inconsistently. 
The error message will be on the Transaction Details page and similar to: 

Step 'https://<MonitoredSiteName>' failed: No element was clicked.



Playback in Modern Player fails with this message in 2024.x, this is known issue and engineering are working to apply fix. Workaround is to use Deprecated Recorder or remote the extra click step.

image.png

Product section

Web Performance Monitor

Cause

  • Active directory accounts are required for authentication to the website.
  • Element to be clicked on was not found on the page during playback of the Transaction.
  • WPM Recorder is intercepting all events, even the ones that are triggered programmatically by the websites code. This is not intended behavior, as often the internal website code is setting state on some elements that are not reachable, and playback of such actions will fail. (confirmed as bug)

Resolution

For Single Sign On / Windows Authentication Websites:

This message is often received when the transaction requires a specific user to login to the site. This is easily missed with Automatic Windows Authentication because typically, the WPM Recorder is launched as the currently logged in user who as access to the website. When the recording is then assigned to the Player, the transaction is played back using the local WPM users. Instead, domain accounts should be configured on the Player location. Please consult the appropriate documentation: Configure Domain Accounts per Player Location.
 


Workaround 1:

It is recommended to use the new WPM Recorder and not the deprecated Recorder. This is available on WPM version 3.0 and later. 
Implement an X,Y Capture method to the Recording. These Instructions are for the 3.0+ Recorder.
  1. Open the Recording in the WPM Recorder
  2. Before the failing step: select 'Continue recording from here' 
  3. Click X,Y Capture in the top tool menu
  4. Click the link that was failing before
  5. Continue building out the remainder of the Recording
  6. Save the Recording to overwrite the existing Recording file
Side note:
In some rare cases, the mouseover feature is also useful. While in Recording mode, hitting the Ctrl + ~ (some keyboards could be Ctrl + ' (single quotes) or Ctrl + ` (backquote)) keys will record the location of the mouse cursor location. This can be useful when recording some mouseover menus, especially where clicks are not necessary, only a mouseover action.

You should see "Hover over" on the transaction steps.
image.png

These Instructions are for the deprecated Recorder.
  1. Start WPM Recorder(deprecated) and maximize it
  2. Start recording by navigating to about:blank page
  3. Enable XY mode
  4. Click anywhere on the blank page
  5. Disable XY mode
  6. Navigate to the website
  7. Continue recording additional steps
NOTE: These steps should force the size of the screen during playback
 

Workaround 2:

You may also add a wait condition before the failing step. 
  1. Open Recording in the WPM Recorder
  2. Click the 3 dots next to the failing step
  3. Add wait condition before
  4. Save Recording.
If none of the above workarounds works, please log a ticket with Support as it could be a bug. Support, please check pro-content area for bug info.