A short catalogue of the errors you are most likely to see during scan configuration and what each one means.

target_unreachable#

Pentrova could not reach the target base URL within the connection timeout. Usually caused by a firewall rule or a VPN-only environment. Add the published Pentrova egress range to your allow list so the hosted runner can reach the target.

auth_profile_failed#

The configured login flow did not produce a valid token. The log attached to the error includes the failed step. Common cases are stale credentials, a rate-limited identity provider, or a login form whose fields have changed since the profile was authored.

sandbox_reproduction_unavailable#

A Critical or High finding could not be reproduced in the sandbox — usually because the sandbox image is missing the runtime the exploit needs. The finding is still reported with its captured request/response evidence; contact support if you need the sandbox reproduction for a specific runtime.

fix_confirmed#

A previously reported finding no longer reproduces against the current build. This is not an error — it almost always means your fix landed. Treat it as confirmation and close the ticket.