BrowserAct

Product details
111315755532547057380111315755532547057380
111315755532547057380PLUS
Mar 2, 2026

Q: BrowserAct fails to identify an element

Hi, can you please help with my workflow 82683458862844784. You can see in the logs that this workflow keeps failing with the error "Find element failed". This is about the "Message" button. However, even the screenshot shows that the button is clearly visible. Whenever I'm running the automation through make.com, it's failing. I've tried different variations of the prompt to explain where the button is. Please help fix this.

Founder Team
Claire_BrowserAct

Claire_BrowserAct

Mar 3, 2026

A: Hi there — thank you for sharing the workflow ID.

After reviewing the logs, it appears that although the button is visible in the screenshot, the page may not have been fully ready when the click step executed.

Recommended fix:
Add a Wait step before the “Click Message” step to allow the page to finish rendering and ensure the element becomes fully interactable. This typically improves the success rate significantly.

If the issue persists after adding the Wait step, please reach out to us via Discord or email support with the latest run details, and we’ll assist you further.

Please feel free to send over any additional questions anytime.

Share
Helpful?
0
Log in to join the conversation