Skip to content

Commit 330c144

Browse files
Merge branch 'master' into justinegeffen-cloud-releases
2 parents f5349f2 + c5f4995 commit 330c144

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

platform-cloud/docs/compute-envs/aws-batch.mdx

+2-2
Original file line numberDiff line numberDiff line change
@@ -374,7 +374,7 @@ Seqera Platform compute environments for AWS Batch include advanced options to c
374374
- Specify a **CloudWatch Log group** for the `awslogs` driver to stream the logs entry to an existing Log group in Cloudwatch.
375375

376376
:::caution
377-
Our platform makes every effort to terminate compute resources when a Nextflow pipeline completes or is canceled. However, due to factors outside of our control — including user-defined workflow logic, transient cloud faults, or abnormal pipeline exits — residual resources may persist. We provide visibility and APIs to detect and resolve these states, but the customer retains responsibility for final cleanup and ensuring compute environments behave according to platform expectations.
377+
Seqera platform is designed to terminate compute resources when a Nextflow pipeline completes or is canceled. However, due to external factors — including user-defined workflow logic, transient cloud faults, or abnormal pipeline exits — residual resources may persist. While Platform provides visibility and APIs to detect and resolve these states, customers are responsible for final resource cleanup and ensuring compute environments operate according to Platform expectations.
378378

379379
From Nextflow v24.10+, compute jobs are identifiable by Seqera workflow ID. If you search your AWS console/CLI/API for jobs prefixed by a given workflow ID, you can check the status and perform additional cleanup in edge case scenarios.
380-
:::
380+
:::

platform-enterprise_versioned_docs/version-25.1/compute-envs/aws-batch.mdx

+6
Original file line numberDiff line numberDiff line change
@@ -372,3 +372,9 @@ Seqera Platform compute environments for AWS Batch include advanced options to c
372372
- Add an execution role ARN to the **Batch execution role** field to grant permissions to make API calls on your behalf to the ECS container used by Batch. This is required if the pipeline launched with this compute environment needs access to the secrets stored in this workspace. This field can be ignored if you are not using secrets.
373373
- Use **AWS CLI tool path** to specify the location of the `aws` CLI.
374374
- Specify a **CloudWatch Log group** for the `awslogs` driver to stream the logs entry to an existing Log group in Cloudwatch.
375+
376+
:::caution
377+
Seqera platform is designed to terminate compute resources when a Nextflow pipeline completes or is canceled. However, due to external factors — including user-defined workflow logic, transient cloud faults, or abnormal pipeline exits — residual resources may persist. While Platform provides visibility and APIs to detect and resolve these states, customers are responsible for final resource cleanup and ensuring compute environments operate according to Platform expectations.
378+
379+
From Nextflow v24.10+, compute jobs are identifiable by Seqera workflow ID. If you search your AWS console/CLI/API for jobs prefixed by a given workflow ID, you can check the status and perform additional cleanup in edge case scenarios.
380+
:::

0 commit comments

Comments
 (0)