Stopped at "Needs Action"

When a person's input is needed during a run, the test stops with Needs Action. For example:

• Login is required (you haven't logged in yet, or the previous login expired)
• A screen for entering a two-step verification code appeared
• The test includes a step for a person to perform (awaitUser)

To continue

What's needed is shown below the small window in the corner of the screen.

• If you're asked to enter a value, enter it in the field and choose Submit and Continue. The value is not kept in run logs or other logs.
• If you're asked to do something in the browser, follow the on-screen instructions and choose Continue.
• If you're asked to log in, use the login screen shown in the Browser in the main area and choose I'm Logged In. → When login is required

When the app window isn't in front, an OS notification appears. Choose the notification to bring echo to the front and go to where action is needed. The Dock / taskbar icon also shows the number of tests that need action.

Stop it from happening every time

If it stopped for login, save the login state so tests run logged in for as long as that state is valid on the service side.