A PDF remediation job made be unsuccessful, due to hitting a daily limit, Adobe failure, or other reasons. We need a way to reset the remediation_started_at and remediation_job_uuid fields on FinalSubmissionJob so that files can have remediation attempted again.
Some possibilities:
- In the remediation results controller, the failure path could reset the fields if certain conditions are met. For example, if the error message is about the Daily Limit (or other topics where we want to retry), the fields could reset.
– A rake task where a FinalSubmission file with a remediation_started_at date older than 24 hours but no remediation version has its fields cleared. The only danger is if a pdf is unremediable for some reason, we could keep trying to remediate over and over. If there's some error messaging we get back from Adobe that indicates that it is futile to try this file again, we should consider saving this in our db...perhaps a flag like can't remediate.
A PDF remediation job made be unsuccessful, due to hitting a daily limit, Adobe failure, or other reasons. We need a way to reset the remediation_started_at and remediation_job_uuid fields on FinalSubmissionJob so that files can have remediation attempted again.
Some possibilities:
– A rake task where a FinalSubmission file with a remediation_started_at date older than 24 hours but no remediation version has its fields cleared. The only danger is if a pdf is unremediable for some reason, we could keep trying to remediate over and over. If there's some error messaging we get back from Adobe that indicates that it is futile to try this file again, we should consider saving this in our db...perhaps a flag like
can't remediate.