Limitations of UI Automation in n8n Execution Mode

Hi team,
I’m a QA Automation Engineer currently working on automating n8n workflows. I’d like to know if there are any known limitations when n8n is in Execution Mode that could affect automation.
For example, I noticed that some visible locators cannot be captured while a workflow is executing.

Describe the problem/error/question

Hi team,

I’m a QA Automation Engineer currently working on automating n8n workflows. I’d like to know if there are any known limitations when n8n is in Execution Mode that could affect automation.

For example, I noticed that some visible locators cannot be captured while a workflow is execute mode.

What is the error message (if any)?

Please share your workflow

logs_colum_locator = self.page.locator("[data-test-id='logs-overview-body']")
expect(logs_colum_locator).to_be_visible()

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.