-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Challenge moved back to draft status after some time after activation #1290
Comments
Now this can be experienced in QA challenges as well |
@ThomasKranitsas , in production, the challenge keeps moving back to draft always and hence doesn't allow the challenge to be launched and we cannot move forward. In dev, once we re approve and relaunch a couple of times and open the registration and submission phases in OR, the challenge is good and doesn't move back to draft. But in production, it seems to be always going back to draft |
This issue is still happenning. challenge.back.to.draft.mp4 |
Observing this issue very often still, here is a video recording of the observation today: Draft.2.mp4 |
QA comments: Dev env. Quality Assurance Both types of challenges are moving in a draft. |
On production, QA challenges are moving in draft https://challenges.topcoder.com/projects/32232/challenges/80606449-28f4-44bb-8826-9ca1bd14ab93/view |
On Dev Env, MM challenges are also moving back to Draft status. |
This issue is now happenning only in the Self services challenges. Cannot activate any challenge from today. 2022-05-10_11-31-29.mp4 |
jira issue here: https://topcoder.atlassian.net/browse/PROD-1997 |
Challenge moved back to draft status after some time
The text was updated successfully, but these errors were encountered: