reCAPTCHA ignores “Omit challenges in a multi-step/preview workflow…" setting

Edited the issue as further testing bore out the fact that adding the CAPTCHA element to a specific page in the Webform mitigates this issue. A user would only need to redo the reCAPTCHA if they navigated back to the page with the CAPTCHA.

So there is still an issue here as the Math challenge type behaves as expected, i.e. once completed, do not need to redo.

Confirming this issue! For us it always happens on the second webform page already, without the user having to go back to the first step.

We placed the CAPTCHA Webform element at the root level, before the Submit button, is that correct?
Math captcha 100% works as expected and doesn't block the form, while the multistep form simply can't be proceeded using reCaptcha

Gaining priority for that reason.

Update: This can be mitigated by moving the reCaptcha INTO the first step and NOT having it at the top level of Webform elements before the submit button.

So it *might* also be a Webform issue, if it doesn't happen in other Multistep forms, I'm not sure. But still unexpected, so I'll keep the status.

So it *might* also be a Webform issue, if it doesn't happen in other Multistep forms, I'm not sure. But still unexpected, so I'll keep the status.

I'm facing the same problem with my custom multistep forms.

One observation is that the persistence mechanism and the mentioned option in the captcha module rely on the captcha status stored in the captcha_sessions table. However, it appears that the captcha status is not being updated at all within the ReCaptcha module.

Additionally, I'm unsure whether the ReCaptcha module needs to perform the action mentioned. It might be the responsibility of the captcha module. The captcha status isn't managed if the cacheable attribute during the generation operation is set, which is the case with ReCaptcha.

To me, it makes more sense for the captcha status to be managed entirely by the captcha module.