Automation detail, runs and editing

Gotchas and known limits

• The Logs dialog's panel should keep its content reachable at every width (F23.run-logs-modal). Known failure (reproduced 2026-10-08): with a long task summary (the dialog drops the outcome_summary line breaks, so ask for about 1,500 characters, for example 12 lines of about 120 characters), the panel (max-h-[80vh]) does not scroll, and at phone the Output/Error tabs and the Output box sit below the viewport (browser bbox 'role=dialog >> role=tab[name="Error"]' insideViewport false, and browser scroll cannot reach it). At desktop that run still fits; about twice as much text pushes the Output box up to about 200 px below the panel. A short run fits at desktop; at phone even a ~200-character summary with metadata leaves the Output box about 15 px below the panel (#18173). browser bbox 'role=dialog' measures the full-screen wrapper, not the panel: measure the panel with browser eval.
• The detail page has no main landmark: browser snapshot 'role=main' times out. Snapshot the page, or scope by section headings (role=heading[name="Configuration"] >> xpath=ancestor::div[2]).
• The kebab menu has no test ids; role=list >> has-text=Tarball scopes the detail kebab (the dashboard kebab has no Tarball, so F21 uses has-text=Export).
• Both the X and the footer button of the Edit dialog are named Cancel; use testid=edit-automation-cancel for the footer and role=form[name="Edit automation"] >> xpath=.. >> role=button[name="Cancel"] >> nth=0 for the X. The dialog has no role=dialog.
• Known defect: Escape does not close the Edit dialog (the handler sits on the non-focusable backdrop div) (#17563). The delete confirmation, by contrast, is a role=dialog that Escape closes.
• Known defect: at phone height the Edit dialog has no max-height or scrolling, so its title, X and Save are clipped and unreachable by scrolling (#17563).
• Known defect: clearing Time of day on a preset schedule is silently ignored (#17948); Save closes the dialog with no request and no message.
• On a local backend the Logs dialog reads every run's output from the server-level /api/bash/bash_events/search, with or without a conversation. It caches what it fetched: reload before checking its requests with browser network.
• Known defect: prompt runs also have a bash_command_id, so every row shows the logs icon, and a prompt run that ended without a conversation is labelled as a script run (F23.run-no-conversation) (#17948).
• The automation service (1.19.0 here) keeps repos and plugins only under preset_metadata; the UI reads them from there. Repositories show owner/repo without the host (a GitLab URL reads like a GitHub one), a repo without a ref gets no badge, and Export keeps only the first repository (all plugins). The Notification field reads a top-level notification that the service has no field for, so it never renders on a local stack (#16644 tracks removing or mapping it).
• The Schedule field shows the raw cron (0 9 * * *) and no timezone: the service returns no schedule_human and no top-level timezone, so the Edit dialog also omits its Timezone: hint.
• run-phase never appeared in the log here (phase_code stays null on the local service), so the phase chip is not reachable on this stack.
• An LLM profile that does not exist (model: "qa-no-such-profile") does not fail the run: it ran and succeeded with the active profile. Use timeout 1 to get a failed run; it takes several minutes to fail.
• Load more in the log (F23.activity-log-more) needs more than 20 runs of one automation; at about 35 s and one model call each it is left out of a normal pass (not-run).
• The script section needs a tarball automation. The account-free way to get one is F22's Daily news digest bundle entry (it uploads its bundle and creates the automation); the custom-automation Upload tarball action needs a file you pack yourself. Its Edit dialog still shows an empty Prompt field next to the cron, although a script automation has no prompt.
• Starting… on Run now lasts only for the dispatch request (under 50 ms locally); --observe does not catch it.
• The run row is a plain <a href>, so opening a run's conversation reloads the whole app (a document request in browser network), unlike sidebar navigation.
• A 404 detail request is retried three times before Automation not found shows (about 7 s of skeleton) (#17948); wait with wait-text, not count.
• browser fill on the Timeout spinbutton with letters fails in Playwright and, after its 30 s retry, the dialog was found closed; use numeric values (1.5, 0, 1801) to reach the timeout errors.
• The Tarball download is named <name>.tar (spaces become _) but is gzip-compressed (#17948); browser downloads --inspect does not list tar entries, so inspect it with tar -tzf.
• Debug with OpenHands starts a real agent with the openhands-automation skill and the automation API key. It acts on live automations: here it looked up QA_F23 Fail by name (a newer fixture with the same name), PATCHed its timeout back to 600 and dispatched it, which adds runs and conversations. Stop it once it has started: on its page control-openhands browser click 'testid=stop-button', then control-openhands conversation wait <id> --until paused,finished,idle --timeout 45 (paused).
• A successful run leaves a conversation <name> — <UTC timestamp> that stays after the automation is deleted (conversations family owns deleting it).