Closed AlbertoCasasOrtiz closed 3 months ago
Should we create a new flag for that case?
Maybe we should, and if it's been in the "Waiting for server" state for a long time (e.g., 24 hours) we then ask to reprocess?
if it's been in the "Waiting for server" state for a long time (e.g., 24 hours) we then ask to reprocess?
Yes, that would work and would give us more control over states. In the current version, it asks for reprocess only if it has been in the "processing" or "queued" status for 6 hours (I choose randomly). I think we could add the "waiting for server" status to it and change it for 24 hours.
I changed the time to 24 hours as we discussed, and I found a solution for the Waiting for Server" status.
If the processing flag or the slurm flag exist for more than 6 hours, tell the user to reprocess.
@nickbianco I am not sure how should we procced with the "Waiting for server" status (#248), since there are no flags or files that I know of that we can check for times. In the code, it is in "Waiting for server" status only if there are no other flags, like the processing, queued, error or results flags present.
Should we create a new flag for that case?