Automations dashboard and actions

Gotchas and known limits

• Both sub-page navs are always in the DOM (one hidden by CSS). Unscoped testid=automations-navigation-templates is a strict-mode violation; scope it with testid=automations-navbar-desktop >> or testid=automations-navbar-mobile >> .
• The pin toggle is invisible until the Automate item is hovered on a fine pointer: browser hover 'testid=sidebar-automations-link' before clicking it. The pin is stored per backend and org in localStorage (oh:pinned-home-route:<backend>:<org>); unpin before leaving the run.
• testid=dropdown-trigger is reused by the backend selector, the Filters button and every inner dropdown. Always scope it (testid=automations-filters >> testid=dropdown-trigger >> nth=0 for the Filters button, testid=automations-filter-status >> testid=dropdown-trigger for a field).
• The Filters popover stays open while choices change and closes only on a click outside it or on the Filters button; Escape does not close it. Open, it covers the right part of the list (in list view the first rows' Play buttons): close it with a click on role=heading[name="Dashboard"] before clicking row or card controls.
• A card whose automation was deleted elsewhere stays on the dashboard after its Run now fails with Automation not found. Expected: the card drops out once the dispatch returns 404. Known failure: nothing refetches the list after the failed dispatch, so the card stays until a reload or another list refetch (still there 2 minutes later) (#18062).
• The delete confirmation has no test ids; scope it as the named dialog role=dialog[name="Delete automation"]. It opens with focus on Cancel.
• Delete closes the dialog at once and shows no success toast; confirm with a reload. Turn off on the dashboard never asks for confirmation (home cards do).
• The kebab menu has no test ids; role=list >> has-text=Export is the reliable scope. A card's own Run now has the same accessible name as the kebab item, so scope Play to the card.
• Imported automations are always disabled (Import automation says so), and Run now is disabled until you Turn on. Use the yearly cron 0 0 1 1 * or an event trigger so an enabled fixture never fires by itself, and turn it back off.
• Run now uses the active LLM profile when the automation's model is Active profile. A successful run creates a conversation titled <automation name> — <UTC timestamp> that stays after the automation is deleted. Delete it separately (control-openhands conversation list, conversations family) to leave the run clean.
• A timeout of 1 s does not fail fast: the run sat in Installing dependencies and failed with Timed out: command timed out or was killed about 3-4 minutes after dispatch. Budget for that when you need a failing run for Needs attention.
• The Automations tile counts only loaded pages: with 51 automations it reads 50 until Load more is clicked, although the API total is 51.
• The row health dot and label reflect the latest run only; a disabled automation with no runs reads No activity yet, not Disabled.
• In grid view a cron automation without schedule_human shows the pill cron, while list view shows the raw expression (0 0 1 1 *).
• The view mode persists in localStorage (openhands-automations-view), and the toggle is disabled when the org has no automations. Switch back to Grid before deleting the last automation, or the next run starts in List.
• Filters, search and sort are page state only: a reload resets them.
• service stop automation stops only this run's automation service; restart brings the whole stack back with the same state and the browser on the same page. Run control-openhands doctor afterwards.
• The Automation dispatched toast lasts only a few seconds: run browser wait-text 'Automation dispatched' right after the click, not after a long --observe window.
• browser screenshot --full-page at phone width does not capture below the fold, because the page scrolls inside the main pane; screenshot sections or use bbox.