Hello! After two approvals, the GitHub CI suddenly triggered `Launch workflow via Seqera Platform`. Does anyone know if this is expected? I cannot see a Nextflow error in the logs, only the Seqera launch step:

Run seqeralabs/action-tower-launch@v2
  with:
    workspace_id: 59994744926013
    access_token: ***
    compute_env: aws_ireland_fusionv2_nvme_cpu_spot
    revision: dev
    workdir: <s3://nf-core-awsmegatests/work/bacass/work-dev>
    parameters: {
    "hook_url": "***",
    "outdir": "<s3://nf-core-awsmegatests/bacass/results-dev>"
  }
  
    profiles: test_full
    api_endpoint: <https://api.cloud.seqera.io>
    pipeline: <https://github.com/nf-core/bacass>
    wait: false
/usr/bin/docker run --name dc4a5325cf1a6eed4587b1a139fa846dfdb5_c7ae04 --label 99dc4a --workdir /github/workspace --rm -e "INPUT_WORKSPACE_ID" -e "INPUT_ACCESS_TOKEN" -e "INPUT_COMPUTE_ENV" -e "INPUT_REVISION" -e "INPUT_WORKDIR" -e "INPUT_PARAMETERS" -e "INPUT_PROFILES" -e "INPUT_API_ENDPOINT" -e "INPUT_PIPELINE" -e "INPUT_RUN_NAME" -e "INPUT_NEXTFLOW_CONFIG" -e "INPUT_PRE_RUN_SCRIPT" -e "INPUT_WAIT" -e "TOWER_WORKSPACE_ID" -e "TOWER_API_ENDPOINT" -e "TOWER_ACCESS_TOKEN" -e "TOWER_COMPUTE_ENV" -e "PIPELINE" -e "REVISION" -e "WORKDIR" -e "PARAMETERS" -e "CONFIG_PROFILES" -e "RUN_NAME" -e "NEXTFLOW_CONFIG" -e "PRE_RUN_SCRIPT" -e "WAIT" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e "ACTIONS_RESULTS_URL" -e "ACTIONS_ORCHESTRATION_ID" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp":"/github/runner_temp" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/bacass/bacass":"/github/workspace" 99dc4a:5325cf1a6eed4587b1a139fa846dfdb5
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed

  0      0   0      0   0      0      0      0                              0
100   1104 100   1104   0      0   2555      0                              0
100   1104 100   1104   0      0   2554      0                              0
100   1104 100   1104   0      0   2554      0                              0

I’m not sure if this means the pipeline failed, or if it only failed while launching/submitting the run to Seqera. Is this relevant for proceeding with the merge?

yes this is expected on release PRs to make sure the pipeline runs on big data. We are only triggering it after approval and not on every push to make sure we contain costs a bit

Thanks! Just to be sure, the GitHub check is still failing at the Launch workflow via Seqera Platform step, so I’m not sure if the run was submitted successfully or if I need to fix something. Should I check anything manually in Seqera Platform? If so, where should I look?

if the CI failed the run was not submitted successfully. Note: a green tick on github just means that the submission was successful , not that the run was successful. If you have the latest template you should get a slack notification on success/failure of the pipeline and you can check in platform. You should see it here: https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch I just added you as a user

I see thanks!!! I though the pipeline was causing the error due some issue 😅

ran successfully: https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch/4ZGpJnk1vWAJWI/tasks looks like the slack notifications are not yet activated are you on the latest template?

not yet, I will update to the latest template shortly