Read Logs
Records the device log around the part of the run you care about — Android logcat, iOS syslog — and saves it as a file.
Capture device logs (Android logcat / iOS syslog). Start begins a capture; a Stop node — or the workflow ending — saves it. A Start can also self-bound by time or line count.
Reach for it when
- A crash or an ANR you need the stack for.
- Proving what the app actually did while the screen looked fine.
Every setting this block has. A field marked only when appears once you have chosen the mode above it — those are alternatives to each other, not extra things to fill in.
- Actionstarts at Start capturingStart capturingStop & save
- Stop capturingstarts at At a Stop node (or when the workflow ends)
When this capture ends. With no Stop node it keeps recording until the workflow finishes, then saves.
At a Stop node (or when the workflow ends)After a set timeAfter a number of linesonly when Action = Start capturing
- Capture forstarts at 10s
only when Action = Start capturing, Stop capturing = After a set time
- Linesstarts at 500
only when Action = Start capturing, Stop capturing = After a number of lines
- Tag filterstarts at —
Only keep log lines containing this text.
only when Action = Start capturing
- Min levelstarts at Verbose (all)
Keep lines at or above this priority (Android).
Verbose (all)InfoWarnErroronly when Action = Start capturing
Start capturing before the interesting part
Everything the device logs from here on is kept, subject to the filters below.
Read LogsSettings ActionStart capturingStop capturingAt a Stop node (or when the workflow ends)Tag filterOnly lines containing thisMyAppMin levelWarnSay when it ends — or let the workflow end it
A Start can bound itself by time or by line count. With neither, it keeps recording to the end of the workflow and saves then.
Min level = Warn Stop and save where the interesting part ends
A second Read Logs node with Action = Stop & save writes the capture out.
one capture, two copies of this node - Read LogsAction = Start capturing
- …the steps you want the log for
- Read LogsAction = Stop & save
- The captured lines, and a saved log file the notify nodes can attach.
- A capture with no Stop node is not a leak — it ends with the workflow. It is only a surprise if you expected it to stop at the next step.
- Filtering by tag and level before the fact is cheaper than reading 20,000 lines afterwards, but you cannot get back what you filtered out.