A Celery captcha task has one rule that shapes everything else: it must solve from scratch on every attempt. Celery gives you at-least-once delivery, so a task can run twice, and a CapSkip result can be read once. Store a captcha id and resume from it after a retry and you get nothing back. Solve, use the token and finish, all inside one task body.<\/p>\n
# pip install capskip\r\npip install -U celery[redis] capskip<\/pre>\n<\/div>\nStep 1: the task<\/h2>\n
The whole solve is one call. The SDK submits, polls and returns the token, so there is no id to carry between steps and nothing to persist.<\/p>\n
\n# pip install capskip\r\nimport os\r\nfrom celery import Celery\r\nfrom capskip import CapSkip, NetworkException\r\n\r\napp = Celery("solves", broker="redis:\/\/redis:6379\/0")\r\n\r\n# CAPSKIP_HOST is the solver machine. Loopback only works if the\r\n# worker runs on the same Windows box as CapSkip.\r\nsolver = CapSkip(\r\n host=os.environ.get("CAPSKIP_HOST", "127.0.0.1"),\r\n port=int(os.environ.get("CAPSKIP_PORT", "8080")),\r\n apiKey=os.environ.get("CAPSKIP_API_KEY", "capskip"),\r\n)\r\n\r\n@app.task(\r\n bind=True,\r\n autoretry_for=(NetworkException,),\r\n retry_backoff=True,\r\n max_retries=3,\r\n soft_time_limit=330,\r\n time_limit=360,\r\n)\r\ndef solve_and_submit(self, sitekey, page_url):\r\n result = solver.recaptcha(sitekey=sitekey, url=page_url)\r\n return submit_form(page_url, result["code"]) # token, used here<\/pre>\n<\/div>\nNote what is not in there. No captcha id in the return value, no second task to submit the token, no result stored for later. The token is used in the same task that made it. The reason is timing rather than tidiness, and it is covered under retries below.<\/p>\n
That call is reCAPTCHA v2. The other types CapSkip supports are the same shape: pass invisible or enterprise set to 1, or version set to v3 with an action, or call turnstile or geetest instead. The full surface is on the Python CAPTCHA solver page<\/a>.<\/p>\n
Step 2: two time limits, and where to put them<\/h2>\n
Celery has no time limit by default, on either setting. That is the wrong default for a task that waits on a network service, because a stuck solve occupies a worker slot forever.<\/p>\n
Set both, and set them above what the SDK itself allows. CapSkip gives a reCAPTCHA, Turnstile or GeeTest solve three hundred seconds and an image CAPTCHA one hundred and twenty, both configurable on the client. If the soft limit fires first, Celery raises SoftTimeLimitExceeded inside your task and you lose the SDK’s own TimeoutException, which is the more useful signal because it tells you the solver was reached and did not finish.<\/p>\n