Expand description
The verify phase: asking the study registry what became of a submission.
The only way out of submission_uncertain. Nothing here fails a row: the attainment may exist,
and a failed row is one an admin retries, which for an uncertain submission would mean sending
it twice. The one way back to import is Suotar itself answering notRegistered.
Modules§
- decide 🔒
- What a verify answer does to its row.
- lease 🔒
- Leasing the rows a verify iteration asks about, so no concurrent iteration asks about them too.
- poll 🔒
- Polling what became of the submissions that have an attainment id to poll by.
- recovery 🔒
- Looking for what a submission we lost track of would have created.
Functions§
- run 🔒