Synchronized starts
ReadyThe edge service starts each attempt. Load tests include thousands of learners who start in the same period.
QFlowLearn Delivery
Publish an assessment, let learners complete it in their browser, and review their responses and submissions. Connection-recovery records help your team follow up when an attempt needs attention.
Follow the learner's assessment
- The learner opens an assignment with the required access.
- The delivery service loads the published assessment.
- The learner answers questions and submits the attempt.
- The service records submission status and processes results.
Choose the access path
For LMS delivery, verify the course launch, roster, and grade return. For standalone delivery, establish assignment access, learner identity, and result retrieval.
Plan your delivery setup →See the learner interface
Make connection requirements explicit
Continuing an active attempt after a connection drops differs from starting an assessment offline. Review supported recovery behavior, local storage requirements, and submission receipts for your deployment.
Inspect network recovery →For a proctored exam, include browser restrictions and on-site procedures in the requirements review. Confirm the exact Safe Exam Browser configuration and evidence required by your program.
Handle assessment-day failures
QFlowLearn Delivery tests concurrent starts, connection failures, content corrections, and audit records. The load tests include thousands of concurrent learners.
Deadline submissions
ReadyEach submit request gets a durable receipt. A Cloudflare queue processes the requests and prevents duplicate work.
Connection drops
ReadyThe browser records work in IndexedDB before transmission. QFlowLearn Delivery restores and transmits queued work after a reload or reconnection.
Stale tabs and duplicate submits
ReadyThe attempt authority and submit keys reject a state change from an old browser session.
Post-publication edits
ReadyQFlowLearn Delivery does not change a published assessment version. A correction creates a new version and an audit record.
Bad questions and wrong keys
ReadyRescoring uses an overlay on the attempt evidence. QFlowLearn Delivery keeps the original responses and records the scoring change.
Late submits and reconnects
ReadyQFlowLearn Delivery records the learner action. It then compares the time and policy with the attempt ledger.
Scoring corrections and result challenges
ReadyQFlowLearn Delivery calculates final scores from the attempt evidence. The attempt ledger supports audits, reviews, and rescoring.
Operations evidence
The packet gives evidence for launch, submit, reconnect, scoring, export, and recovery operations. Evaluators can review the status of each operation.
| Operational scenario | Evidence to include | Status |
|---|---|---|
| Synchronized start window | Load-test summary, launch plan, edge bootstrap path, package version proof, monitoring signals | Ready |
| Deadline submission window | Load-test summary, durable receipt sample, idempotency behavior, queue and scoring handoff | Ready |
| Bad connection or replayed submit | IndexedDB recovery store, offline replay E2E, reload and tab reopen tests, degraded submit recovery test | Ready |
| Stale tab or duplicate submit | Per-attempt authority test and stale-session reconciliation evidence | Ready |
| Bad item or wrong key | Immutable content version, scoring overlay, correction provenance sample | Ready |
| Incident and recovery response | Escalation roles, support timeline, audit export, remediation queue view | Evidence in progress |
| Load-test evidence | Load-tested pattern for thousands of concurrent learners on Cloudflare serverless primitives | Ready |
Cloudflare services
Cloudflare Workers process launch and delivery requests. A Durable Object controls each attempt. Cloudflare Queues process submit requests.
Workers at the edge
Workers process bootstrap and item delivery requests at Cloudflare locations.
Durable Objects per attempt
One Durable Object controls each learner attempt. Old tabs and duplicate submit requests use the same authority.
Queues for submit
The queue records submit requests and prevents duplicate work. Scoring and export operations use the queued requests.
Attempt evidence
The attempt event ledger is the source record for final scores. It preserves the event history needed to investigate a result, replay recovery behavior, or apply rescoring.
The public delivery hostname is take.qflowlearn.com.
Review the runtime contract
Technical evaluators can review the runtime contract, network recovery evidence, architecture summary, and load test plan.