Repository navigation
fix: a site that emails a code holds the application, and the run note matches the form - #67
Merged
Merged
Conversation
…e matches the form
Catapult's live send reached Greenhouse's "A verification code was sent to ...
enter the 8-character code to confirm you're a human" and was recorded as
"unconfirmed" ("check whether it went through"), though it plainly hadn't gone.
- After a submit the page doesn't confirm, browser_agent reads the page for a
request for an emailed code (_CODE_ASKED_JS) and returns it as code_asked.
- Autopilot holds such a run as needs_you, quoting the page, and says to apply on
the job's page with the run's CV and letter. The tracker note says the same. It
doesn't count toward the daily limit, since nothing was sent.
The run's note was the fill agent's own summary, which said the consent box was
left unticked while the form showed it ticked from the saved answer. Unattended,
nobody checks that summary against the page, so the notes of a filled form now
keep only what Windrush checked on the final form (left blank, still empty,
self-answered); the summary stays when the agent couldn't finish, to say why.
This was referenced Oct 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Catapult's first live send reached Greenhouse's "A verification code was sent to … enter the 8-character code to confirm you're a human". Two things went wrong in how that was recorded:
Greenhouse job boards score each application with invisible reCAPTCHA (mouse movement, typing patterns). Depending on the employer's spam-sensitivity setting, a low score triggers an emailed code (Greenhouse support). A headless browser scores low, so other Greenhouse employers with stricter settings will ask for this too. That check is for the candidate to pass: this PR reports it clearly and does not try to get round it.
What changed
browser_agent
_code_askedreads the visible page, iframes included, for a request for an emailed code.code_asked, with the action "The site asked for a code it emailed you".Unattended notes
autopilot
code_askedrun isneeds_you. The reason quotes the page and says to apply on the job's page with the run's CV and cover letter.Tests
code.html(Greenhouse's wording) reports the sentence;form.htmlwith an unconfirmed submit reports no code and "Couldn't confirm the submission".After deploy
Rebuild the API with
docker compose up -d --build api.