[$50] Closed task opens again after few minutes of closing it - intermittently disappears and reappears in Challenge list

[sandhiyakavi]

Description:

The task closed is opening again after few minutes of closing it.

challenge used: https://challenges.topcoder.com/projects/24943/challenges/77334026-c28b-4ca5-87f7-c9f5bc5ee5cb

cc: @lakshmiathreya

[rootelement]

This task is now closed. Did you force it through, or did it happen on it's own?

[sandhiyakavi]

@rootelement It happened on its own

[lakshmiathreya]

cc @vikasrohit @drasticdpk @acshields - we will need to notify ES so they are aware of this behavior:

1. Task disappears upon closing
2. Reappears but is in Open state
3. Goes to Close state after several hours
4. In some cases - the Task is untraceable in WM though it does appear in Legacy. example - https://www.topcoder.com/direct/contest/detail.action?projectId=30158871

[drasticdpk]

@vikasrohit and Team,
I tried to replicate the above scenario but unable to it.
I am able to create task (start-end) as expected.
Reference : https://www.topcoder.com/challenges/849e4d4f-0c3f-44a9-9ac2-318db739829c?tab=details

Note : As copilot, we have to make private task frequently, will monitor this issue closely .

[acshields]

@lakshmiathreya @vikasrohit - just to confirm, is this happening intermittently or all the time?

[vikasrohit]

This just happened to me for a task @acshields. @rootelement I remember seeing you somewhere said that we have to fix something in WM for it not to happen, however, I am missing that place. Can you please share those details again?

[maxceem]

James suggested the next fix on Slack.

Background

Problem: When creating a task, saving as draft, launching, and closing, it goes back to draft.
Reason: WM sets the start date to tomorrow. This screws up direct/legacy when you activate it and it’s tomorrow, but you activate/close it before that
Fix: When you launch a task, make sure you set the start date to now or slightly in the past. This is a little bit of an issue in WM because i don’t know if there’s a validation or something, but if you create a task, save it, then edit it, it looks like WM sets the startdate in the future again.
Solution: When a task-type is launched (PUT/PATCH status change to Active) set the startdate to now. Tasks will not really need to be scheduled outside of leaving them in draft and not launching them.

Task

All changes below if we create a Task:

1. You shouldn’t be able to select Community Review on a task
2. It should default to Internal Review and reviewer should be set by default to the user who created task
3. Hide the start date field and set the startdate = to the current date/time when activating