Submission stuck in "running" state for 2 days
Submission stuck in 'running' state blocks all future entries for 2 days.
A critical bug in the AI for Industry Challenge competition platform has left user Matthias_VE unable to submit new entries for two days. Their submission (#846) first moved from 'queued' to 'finished', then inexplicably reverted to 'running'. Although results are visible, the stuck status blocks further submissions. In a forum post, Matthias_VE requested an admin to kill the process. The challenge's forum shows multiple recent threads about similar errors, including empty stdout files and submission failures, indicating ongoing platform instability.
This incident highlights the fragility of AI competition infrastructure, where a single stuck submission can derail a participant's entire timeline. With deadlines approaching, unresolved bugs like these risk unfair disqualification and data loss. The platform's slow response—no admin has replied in two days—raises concerns about reliability for critical AI benchmarking events. Competitors need robust error-handling and quicker support to maintain trust in these high-stakes evaluations.
- Submission #846 transitioned 'queued' → 'finished' then back to 'running' without admin intervention.
- The stuck status prevents any new submissions from the affected user for over 48 hours.
- Multiple similar errors (empty stdout, failure logs) have been reported in the same challenge recently.
Why It Matters
A single stuck submission can block a competitor for days, threatening deadlines and leaderboard integrity.