After Begin capture, the engagement is live. Setup is in Running the engagement from the dashboard.
What begin capture changed
After Begin capture, three things hold:
- The fleet is fixed. Capture has begun, so no new device can pair, including re-pairing a revoked or replaced one. Anyone who needs to join or swap machines after this is a conversation with your flowscope contact.
- The start is recorded and the roster is frozen. Begin capture records the start time and fixes who is in the engagement.
- Capture runs on every paired device, inside the allowlist and never the denylist. Each person is shown as a letter label by default.
What to keep an eye on
| Role | EULA | Devices | Joined | |
|---|---|---|---|---|
| alex@yourcompany.com | member | accepted | pairedwindowsv1.0.0ok1m agoqueue 0 · windows 11 | May 12, 2026 |
| sam@yourcompany.com | member | accepted | pairedwindowsv1.0.0stale · last beat 23m23m agostale check-in · windows 11 | May 14, 2026 |
The fleet view shows each device's health indicator and last check-in. Two signals matter:
- permission denied or error: the device is not capturing cleanly. This usually means the agent needs reopening, or that Windows UI Automation has not attached cleanly; the fix is for the participant to reopen flowscope. A short message usually clears it.
- Stale (no check-in for more than about ten minutes): usually just an asleep or offline machine, and it clears when the device returns. A device quiet for a long stretch is worth a nudge, since the participant may have paused or uninstalled it, which is their right.
A glance at the start and end of the engagement, plus any time flowscope flags something, is enough.
The one thing that does need your decision during the run is the App allowlist page. flowscope keeps the list current inside the workflow scope you confirmed, and refers anything it cannot place with confidence to you. Those referrals wait until you accept or reject them, and a real business system left waiting is a workflow missing from the result, so clear them while capture is running rather than at the end.
Actions still available
- Revoke a device. Stops it immediately. Because capture has begun, a revoked device cannot pair again this engagement, so treat a mid-run revoke as final.
- Reveal names. Activity is shown under letter labels by default. When you need the person behind a label, use the reveal control on your organization's home page. flowscope resolves the name on the server and logs each reveal. See Revealing real names.
Participants keep their controls
Throughout the run, each participant keeps the controls in Your privacy and controls: a visible indicator, pause and resume, and the ability to remove flowscope. A participant who pauses or uninstalls shows as quiet or gone in the fleet, which is expected.
When to contact flowscope
Contact support@flowscope.com if someone needs to join or change machines after capture begins, a device stays unhealthy after reopening the app, or coverage does not match the goal. When the period is up: Ending the engagement.