Blockers are not one problem
A portal can stop a run in many ways: a one-time code by email or text, an MFA prompt, a CAPTCHA, an unexpected popup, or a page that needs someone to confirm a decision. A script that treats all of them as an error fails, and someone restarts the job from the beginning.
Ramain models them as states the run can be in. A run can be waiting for a code, waiting for a person or recovering from an unexpected page, and it carries on from where it stopped.
Codes from your own inbox
For one-time codes, the digital worker reads the code sent to an inbox or phone number you control, the same way a colleague would check the team mailbox. The login itself uses credentials you provide from the vault.
When a site needs a person
Digital workers do not bypass security controls. When a site requires a person, for a CAPTCHA, an approval or a judgment call, the run pauses and asks. Someone on your team answers or takes over the live browser, and the run continues with everything it had already done.
Every pause is recorded
Each pause, answer and recovery is part of the run record, next to the recording. An operator can see why a run waited and who unblocked it, and an auditor can see the same thing later.