Phases are closing when they shouldn't

[ajefts]

I created a few test challenges in dev and the Registration/Submission phases seem to have closed shortly after they opened.

Here is an example: https://challenges.topcoder-dev.com/projects/17062/challenges/5a33a6d3-1595-4fc2-9f5c-23b5d940b303/view

Note in Online Review that the "Scheduled End Date" has not been reached on either phase.

STEPS TO REPRODUCE:

1. Create a dev challenge, task, or F2F via work manager.
2. Activate the challenge
3. Make sure the start date in Work Manager is set to the past or a time that will open shortly.
4. Let the challenge open automatically
5. Monitor the status of the phases to see if they switch to closed before they should.

[ajefts]

fyi @rootelement

[ajefts]

Update: I think I just figured out what triggers it. As soon as the start date hits (or if it's in the past) it's updated registration and submission to Closed.

[ThomasKranitsas]

I'm currently working on it... I've added a couple checks so now:

• There should be no scheduled events for non active challenges
• There should be no scheduled events for actions that should have happened in the past.

I'm currently thinking how to handle the scenario when:

• You create a challenge with startDate = now
• After a few minutes it reaches to an active state
• The processor picks up the event and creates the events for future phase changes but the registration/submission phases won't open as their start date belong to the past.