Skip to main content

Version 1.0.4

Release Date: September 20, 2026

Event-Retarget Transfer​

Same-event POST /api/v1/attempts/{attempt_id}/transfer still clones the source event, including event_ends_at. If that event has already ended, the transfer succeeds, but the successor is already past its deadline and the auto-submission collector closes it. That is correct: extending ends_at would rewrite the deadline for every other attempt on the event.

When the owner needs the answers to keep living, they create a new active event on the same quiz and retarget the attempt onto it.

POST /api/v1/attempts/{attempt_id}/transfer-event
{
"event_id": "550e8400-e29b-41d4-a716-446655440000",
"bypass_client": false,
"reason": "recovery session after the original event ended"
}

Owner API key or JWT required. The successor copies the latest answers, stays open, and uses the destination event's deadline and effective config.

Constraints​

RuleFailure
Destination event and source attempt must belong to the same quizAT-411
Destination event must be currently activeAT-412
Quiz question count must still equal the attempt's total_questionsAT-504
Caller must own the quizerror, no leak

Do not edit the quiz's questions before retargeting. A changed question count cannot carry the original answers safely.

Same-Event Transfer Success Code​

POST /api/v1/attempts/{attempt_id}/transfer now returns AT-004 when the cloned event has already ended (HardLimit). HTTP stays 200. The successor will be closed by the collector; hand the participant a recovery event and /transfer-event instead.

Active-event same-event transfers still return 0000.