Skip to main content
A workflow is Python phone-driving code saved in Axilio. Axilio stores the code in numbered revisions and runs it unchanged. A run is one execution of that workflow. Its run ID is also used as the session ID when Axilio claims a phone.

​
Lifecycle

  1. Create a workflow and save its first code revision.
  2. Pull, edit, push, and restore code as new revisions.
  3. Queue one or more runs immediately.
  4. Axilio starts the run on the dedicated phone you selected.
  5. Inspect the run, its phone session, Telemetry, recording, and captured files.
Runs do not currently accept a future start time or recurring schedule. start_timeout_seconds only limits how long a queued run can wait for a phone.

​
Workflow settings

Workflow-level settings become defaults for every run:
  • recording controls video and rolling thumbnails.
  • telemetry controls whether Axilio produces live and retained Telemetry. Set it to false when the run must produce no Telemetry trace.
  • capture controls whether media produced on the phone enters the organization’s Files library.
  • platform selects the target mobile platform.
  • ocr_engine selects the default OCR backend.

​
Next steps

Create a workflow

Save code and manage revisions.

Run a workflow

Queue one or more executions.

Monitor runs

Inspect, watch, cancel, and summarize runs.