Retrying failed submissions in bulk
If a handful of submissions failed at once — say, during a transient hiccup — you don’t have to retry them one at a time. This article shows you the bulk retry options.
From the assessment page
- Open your assessment.
- If there are failed submissions, you’ll see a banner at the top — something like “3 submissions failed.”
- Click Retry all failed.
Marking.ai queues every failed submission for a fresh retry. You’ll see them flip from Failed back to Queued, then Processing, then Marked (assuming the retry succeeds).
From the Activity screen
If you’ve got failures across multiple assessments:
- Open the Activity screen.
- Use the Failed tab to see everything that’s failed.
- Either retry each row individually, or bulk-select and retry from the toolbar.
From Marko
“Retry all failed submissions” works in chat. Marko shows you a preview of what would be retried before running it.
What happens to retries
Each submission’s retry is treated like a fresh marking job:
- Successful retry — status flips to Marked, the result shows up
- Failed again — status stays Failed; the underlying issue probably needs a re-upload or admin help
- Retry quota — we don’t impose retry limits in normal use, but persistent failures usually indicate the file or input needs fixing
When not to bulk retry
If the failure reason is something other than a transient error — missing marking guide, unreadable PDFs — retrying won’t help. Click into individual failures first to see the failure type. If they all show “re-upload required”, a retry isn’t the right move.
Need help?
Click the chat icon in the app or email connect@marking.ai.
FAQs
Does bulk retry use my submissions allowance?
Only successful marks consume allowance. Failed retries don’t.
Can I bulk retry across multiple assessments?
Yes — the Activity screen’s Failed tab covers everything in your workspace. Bulk-select across assessments and retry from there.
What if my retry happens during a marking-engine outage?
We try to spot these and queue retries for after recovery. If your retries are immediately failing during what looks like a wider issue, drop us a line.