Project

General

Profile

Bug #23708

Shouldn' t mark recovery jobs Failed ...

Added by Marc Mengel about 1 year ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
12/05/2019
Due date:
% Done:

0%

Estimated time:
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

Basically recovery launches tend to concentrate failures (at least when the failure is tied to input files), so we shouldn't mark them Failed and stop the workflow, regardless how many fail. So we need to check in update_submission and if we're trying to mark it Failed but we have a parent submission, mark it Completed instead.

History

#1 Updated by Marc Mengel 2 months ago

  • Target version set to v4_3_0

Also available in: Atom PDF