CAPTCHA

It almost never appears at random. The challenge is the visible end of a score built from your exit address, your session history and what your browser answered, and answering it is only the last step.

A CAPTCHA is a test a site shows when it wants proof that a person, and not a program, is asking.

Why the challenge appeared

A challenge is a verdict, not a greeting. Something about the request looked cheap to produce, and the page asked for proof that it was not.

The exit address
A datacentre range, a heavily shared exit or an address with a history of abuse raises the score before a page is drawn.
The session
A brand new profile with no cookies and no history looks like a first visit from nobody in particular.
What the browser answered
Values that disagree with each other, or a browser saying it is being driven, weigh more than any single reading.

Signals a challenge can read here

These are read in your browser as you read this page. A challenge script reads the same ones and dozens more, and it judges the combination rather than any one row.

Il suo dispositivo, adesso

Automation flag: misurazione sul suo dispositivo
Processor cores reported: misurazione sul suo dispositivo
Languages: misurazione sul suo dispositivo
Time zone: misurazione sul suo dispositivo

Letto nel suo browser e mostrato qui. Nulla viene inviato da nessuna parte.

What a flow does when one appears

This is worth knowing before a run is left unattended. A step that looks for an element the challenge replaced finds nothing, and that failure is recorded rather than fatal.

1
The step fails
Its target matches nothing on the page, and the step is written into the run log with its reason.
2
The run carries on
The steps after it still run, against a page that is still asking the question.
3
The profile is marked
Failed steps are counted per profile, so the run is reported failed rather than green.

Answering it yourself

A challenge wants a person, so it wants a window. The workable shape is a flow that pauses at the right moment and a profile that is on screen when it does.

Keep the window
A profile launched with no window has nowhere to show the question, so a first sign in belongs on screen.
Wait for what comes after
A wait step can hold for the element that only appears once the challenge is answered, for as long as ten minutes.
Branch on what you see
A test for an element that is missing lets one side of a branch handle the clean case and the other handle the question.

Often confused with

A one-time code
A code proves you hold the account. A challenge asks whether you are a person, and passing one says nothing about the other.
A ban
A challenge is a question you can answer. A ban is a decision already taken, and trying again does not undo it.
Rate limiting
A limit slows everyone alike and lifts by itself. A challenge is aimed at you and lifts only when you answer it.

What this does not do

ARMANOS does not answer a CAPTCHA. There is no solver in the product and no connection to an outside one, so a challenge is yours to answer in the window.
A run does not halt when a challenge appears. The step that finds nothing is written down as failed, and the steps after it keep going against a page that is still asking.
A profile launched with no window has nowhere to show the question. Work that can raise one belongs in a launch you can actually see.
Nothing here lowers the score that raised the challenge. The exit address, the session history and the hour you work at did that, and each of them is a separate problem.

Check it

The absence of a thing is checkable too: here is the whole list of what a step can be.

Every kind of step a flow may hold, with nothing for challenges among them: apps/desktop/src/lib/rpa.js
A failed step is counted per profile, and a run with failures is not reported green: apps/desktop/src/main/main.js · apps/desktop/test/run-result-honest.js
Waiting for an element runs on the real engine against a real page: apps/desktop/test/сценарий-живьём.js
A profile with no window keeps that choice on every road into a launch: apps/desktop/src/lib/forkEngine.js · apps/desktop/test/скрытый-режим.js

Questions

Does ARMANOS solve captchas?: No. Nothing in the product recognises a challenge, answers one or hands it to a service that would, and the list of step kinds has nothing of the sort in it.
Can I connect a solving service?: The app ships no step that calls one and holds no key for one. If that is what a job needs, it is not something this product provides.
Why is the same profile challenged every time?: Because whatever raised the score has not changed. An empty cookie jar, a heavily shared exit address or a browser that disagrees with itself will each do it on their own.
Does a residential address remove them?: It removes one reason out of several. A clean address in front of a brand new profile that behaves like a script still collects questions.
When should the window stay on screen?: For a first sign in, for anything that can raise a code or a verification step, and for as long as you are still building the flow.

Next to this

Keep the window open where it matters

Profiles, flows and the run log live in the app on your own machine, and a challenge stays a question you answer yourself.

Download ARMANOS How automation gives itself away