A participant's mining status tracks their journey from installing Scribe to actively contributing workflow data. Here's how that journey works:
Mining runs through the Scribe browser extension, the desktop app, or both, depending on how your org is configured. Install happens one of two ways: self-install from a link, or IT-managed via MDM push. Either way, nothing gets captured until the extension or app is actually installed and running on the browser or device the participant uses day to day.
Installing is only step one, though. A participant also has to log in with their Scribe account before any data flows. Once they do, that session is meant to persist - they stay logged in until they explicitly log out or uninstall, unless background capture has gone quiet longer than the org's session limit allows. If someone gets logged out unexpectedly, mining simply stops until they sign back in.
Put installation and login together and you get to "actively mining", but even that takes one more ingredient. A participant only counts as actively mining when the extension or app is on a supported version, they're logged in, and actions are coming through consistently over time.
Where a participant can land along the way:
| Status | Meaning |
|---|---|
| Invite Pending | Invite not yet accepted |
| Incomplete Setup | Invite accepted, but install/login/consent not finished |
| Ready to Mine | Setup complete, mining enabled, awaiting data |
| Actively Mining | Actions flowing in consistently |
| Capture Error | Extension/app is checking in, but actions aren't coming through |
| Paused | Mining intentionally paused by participant or system admin |
When someone's stuck on "Incomplete Setup"
- Confirm the invite was accepted; resend if needed.
- Check the extension or desktop app is installed on the browser/OS they actually use.
- Confirm they’re logged in.
- If consent is enabled, confirm they accepted it.
- Update the app or extension if outdated.
Once complete, the status should change to Ready to Mine, then Actively Mining when data arrives.
When someone's stuck on "Capture Error"
- Confirm they’re working in a whitelisted app; add missing apps in Workflow Mining Settings.
- Check whether action volume is unusually low and whether the issue is new or ongoing.
- Rule out battery saver, VPN, or restrictive network policies.
- If the issue persists, contact your CSM or Support with the participant’s email and organization name.
Knowing when to escalate
Bring in your CSM or Support if Incomplete Setup drags on for days after every step above has been completed, if Capture Error persists after ruling out whitelist and connectivity issues, or if a participant who was previously mining just stops with no change on your end to explain it.