Fix a site profile that has not become active

The profile is queued, capturing or validating.

Capture is still in progress. Capture buttons are disabled while it’s running.

Try this: Wait for the status to change rather than repeatedly submitting or trying to recapture the profile. There’s no guaranteed capture duration.

The profile is in review.

Review is not active. Read any explanation or next step displayed for the profile.

Try this: Follow the displayed guidance. If it gives you no actionable next step, contact support with the profile status and sanitized details listed below.

The profile is failed.

Read the displayed capture reason before retrying. Check whether it points to incorrect target settings.

Try this: Correct wrong settings through Edit target where available. Use Retry capture when the failed profile offers it; don’t retry unchanged settings when the reason identifies an input problem.

Some accounts show Add credit to capture, or Add credit to continue during setup. Follow that prompt if it appears; don’t assume credit is the cause of every failed capture.

Open the profile and use Edit target if it’s available. If you haven’t added a profile, select Add a site. Check these settings against the page you intend to solve:

• Page URL: use the exact HTTPS page where the intended reCAPTCHA runs, not just the site’s homepage.
• Capture action: check the action for that page. In Edit target, this is the action field.
• reCAPTCHA type: choose Enterprise v3 or Regular v3 to match the target. For API requests, recaptchaType defaults to enterprise-v3; Regular v3 uses v3.
• Site key: this is optional and can be auto-discovered. A blank field alone doesn’t mean the profile is misconfigured.
• Navigation URL and Referer: these are optional. Check their saved values if the capture reason points to how the page is reached.

Profiles are specific to a hostname, capture action and reCAPTCHA type. An exact task action selects its profile; other execution actions need one unambiguous capture target. Don’t assume an active profile for a domain covers every action, and confirm that an active profile is available to the workspace making the request.

If the profile is already active and you need to refresh its capture, the control is Recapture, or Sync system profile for a system-verified profile—not Retry capture. A different profile showing active won’t resolve a mismatch in the request.

Task creation returns HTTP 403 and the response says the profile is inactive.

This is a solvethree API response, before you have a usable solution.

Try this: Resolve the matching profile’s status or settings in the console. Handle the non-success HTTP response first; repeatedly sending the same task body won’t activate the profile.

The task is ready, but the target website returns HTTP 403.

This is a downstream rejection, not evidence that the profile is inactive. A target 403 alone doesn’t identify which protection rejected the request.

Try this: Inspect the outgoing target request. Submit the solution using its returned userAgent and secChUa identity and the successful proxy. Don’t mix in another target URL or browser identity; ready means a solution was generated, not that the website accepted it.

If you’re still blocked, contact [email protected] with the product, timestamp, target hostname/action, profile status and displayed capture reason. Include the task ID or requestId if available, plus the HTTP status or task error and a sanitized description of the response. Remove API keys, proxy passwords, tokens, cookies and customer data.