Kobo AutoQA pipeline

Sign in to configure and monitor the pipeline.

AutoQA pipeline checking…
Dry run

Your forms

FormUIDSubmissionsPipeline
Loading…
Pick a form on the Forms tab first.

—

1

Server capability check

What the advanced_submission_post endpoint on this server accepts. The dialect decides the payload shape the worker sends.

Detected dialect —
Raw advanced_submission_schema

            
2

Audio questions to process

Detected from the form definition. Untick any recording you do not want analysed.

3

Languages

4

Preset analysis questions

These are answered automatically by AutoQA for every submission and land in _supplementalDetails. UUIDs are generated once and then kept stable.

5

Apply to KoboToolbox

Writes questions, languages and enabled recordings into the form's advanced_features. Preview first if you are touching a live form.


          
6

Trigger

The interval poller always runs. A REST Service webhook makes it near-instant.

7

Process existing submissions

Last days, max records (0 = no cap)

Connection

Credentials entered here are stored in the pipeline database and take priority over anything in .env. Leave a field blank to fall back to the .env value. The API and worker both pick changes up within a few seconds.

KoboToolbox

Find your token at <server>/token/?format=json while signed in to Kobo.

Webhook

Changing the secret means every already-registered webhook must be re-registered on the Setup tab, otherwise Kobo will keep sending the old one and get a 403.

Admin password

Set with ADMIN_PASSWORD in .env and not editable here — it protects this screen, so a deployment that had it in the database could be locked out with no way back in. Change it in .env and restart; every signed-in session is invalidated.

Queue

Recent submissions

SubmissionFormStageTriesUpdatedDetail
Loading…

Submission detail