fix!:Aviti pipeline won't start when OutcomeFailed in

[gerikson]

Pull Request Names

Follow Conventional Commits

Briefly:
Make sure the PR has a title that adheres to the following scheme:

• fix: description of bugfix.
• feat: description of new feature.
• build: description of changes to the build system or external dependencies.
• chore: description of changes that do not modify src or test files.
• ci: description of changes to CI configuration files and scripts.
• docs: description of changes to documentation.
• style: description of changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc).
• refactor: description of code changes that neither fixes a bug nor adds a feature.
• perf: description of changes that improve performance.
• test: description of changes to tests.

If functionality is broken, append a ! to the type, e.g. fix!: or feat!:, to indicate a breaking change.

Description of Changes

[NavandarM]

Great!, Thank you for taking care of it.
Please update the changes description as the Conventional Commits

feat, fix, built, chore, etc.

[NavandarM]

'-Xmx650G' --> Is it specifically for single cell? If so, we can think of adding the checkpoint if library == single cell then 650G else 400G. What do you think?

[gerikson]

That's a good point, yes it that exact instance was single cell data.