There is a problem--let's say a subject's upload failed due to data quality issue (integer/string mismatch, incorrect integer value -3, -9, whatever). Then we need such a mechanism for that subject that it will be force-retried the next day!
Currently, that incorrect form's hash get stored in {subjectkey}_hashes.txt. The next day, when pipeline finds the hash same, it never retries that file.
There is a problem--let's say a subject's upload failed due to data quality issue (integer/string mismatch, incorrect integer value -3, -9, whatever). Then we need such a mechanism for that subject that it will be force-retried the next day!
Currently, that incorrect form's hash get stored in
{subjectkey}_hashes.txt. The next day, when pipeline finds the hash same, it never retries that file.Link PR #91