Not sure if n8n specific issue, but maybe sb has an idea.
My n8n can execute a python selenium script for web automation.
Workflow A: set some initial data (only when testing), execute the script
Workflow B: set some initial data, call workflow A
Curiously enough the selenium script throws an error only when triggered through the B → A sequence. Adding the execute command node to workflow B directly does work without error.
Traceback of the selenium script execution node says there’s an unexpected alert in the selenium headless browser. I’m curious what could cause the difference in behaviour!
I have a workaround already and it seems to be sth in selenium, so it’s not so crucial, but still I’m wondering…
n8n version: 0.135.1 (–> ok I should probably update also and try again)