Skip to content

Published · Updated

Workflows and schedules ​

Workflows are part of the Pro and Team plans.

Build or record ​

  • Visual editor: add steps such as Open app, Click element, Type or Wait for an element, with conditions, loops and retries.
  • Recorder: do the task once on a phone; the Hub turns your taps and typing into steps that find elements by their text and role.
  • YAML: every workflow is also a readable file you can edit, keep in version control and validate.
  • From an AI task: after an AI task finishes, Save as workflow… under its transcript turns its steps into a workflow that needs no model (Explore with AI, replay without a model).

Run ​

Choose one phone, a group or every phone that matches a filter. The Hub asks you to confirm the number of phones. A workflow runs on phones whose AI and automation switch is On; on a phone that is Paused, or that a person controls, it waits (On, Off or Paused). Start with a dry run to see what would happen without touching the phones. Each run has a timeline with screenshots; open a failed run to replay it step by step.

  • Why it failed: a failed run's replay opens with what most likely went wrong (the app changed, a flaky step, the workflow, the phone or a person needed), the facts behind it and what to do next. Explain in plain words asks a model you added for a short summary (AI with your own model).
  • Flaky workflows get a mark in the Workflows list, from their recent runs; hover it to see why.
  • Videos: the Hub records the screen of each phone a workflow runs on (not in dry runs, and not on a gateway's phones) and keeps the video when the run fails. Choose Always, When the run fails or Never in Settings → System → Videos of test and workflow runs.
  • Device conditions: a Device conditions step sets the phone's language, time zone, clock, dark mode, font size, animations, stay awake or a mock location for the run, and puts them back when the run ends.

More in Flaky tests and failures. To run your existing Maestro, Espresso or Appium tests on your phones, see Test suites.

Schedule ​

Run a workflow at a set time, every few minutes or hours, or once. If a run is missed (the computer was off), choose whether to skip it or run it once.

Safe roll-outs ​

Publish a new version to a few phones first (a canary), then to the rest; roll back with one click.

Approvals ​

Steps can wait for a person's approval, and approval rules can require one for sensitive actions, such as installing apps or anything an AI asks for.