Browser automation runs failed when resumed tabs had zero width, so the editor never loaded
A queued browser automation run completed 40 of 42 items, with the two failures caused by a tab that measured zero width rather than by any site block. Because the window had no width, the comment editor was never built, so the automation had no field to type into. The failures occurred in the tab restored after a session was closed and resumed, while a fresh tab handled the remaining 28 items without issue. The author's revised approach measures the window before each action and refuses to type if the size is zero, opening a new tab instead of reusing a broken one. Refusals are now reported separately from successful sends, with a reason logged for each.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in