These Selenium IDE commands are not supported:
answer on next prompt
choose cancel on next confirmation
choose cancel on next prompt
choose ok on next confirmation
double click at
mouse up at
mouse down at
Mouse right click is not supported.
Temporary user profile for playback
Selenium IDE recordings are made with the current User Profile, but playback is done using a temporary User Profile. This means that some websites that need authentication will not ask for credentials during record session, but the authentication steps will be needed during playback. To address this, the user needs to manually edit the script to insert the commands required for the login process.
One test only supported
One test in each Selenium IDE project is supported by web UI flow.
For Each command
Extra Selenium IDE flow input will be generated if you use for each command. It’s a known issue. You can simply input any value into the extra field. It doesn't impact the playback.
Selenium IDE flow might fail running through the flow if there are some lazy-loaded frames. The recording might playback successfully while testing through the Selenium IDE and might fail while running through the Power Automate infrastructure. Selenium IDE identifies frames by the order they were loaded rather than the actual element order in the document. Playback at runtime selects the frame with the element order index, and this might not match with the Selenium IDE recording index, and the playback can fail. Use a better CSS selector for identifying the frame and parent frame.
Local Playback vs. Playback through Power Automate infrastructure
Local Playback through Selenium IDE might not behave as intended in some scenarios due to discrepancies between Selenium IDE and Webdriver. However, playback at runtime through Power Automate infrastructure might behave correctly.