Skip to main content

Developer tools

When working with the Seqera Platform API and tw CLI, you might encounter the following issues.

API​

Maximum results returned​

{object} length parameter cannot be greater than 100 (current value={value_sent})

This error occurs when you request more results than the maximum page size of 100.

To resolve, paginate the results across multiple API calls with the max and offset parameters:

curl -X GET "https://$TOWER_SERVER_URL/workflow/$WORKFLOW_ID/tasks? workspaceId=$WORKSPACE_ID&max=100" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TOWER_ACCESS_TOKEN"
curl -X GET "https://$TOWER_SERVER_URL/workflow/$WORKFLOW_ID/tasks? workspaceId=$WORKSPACE_ID&max=100&offset=100" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TOWER_ACCESS_TOKEN"

tw CLI​

Connection errors with AWS Batch compute environments​

Creating or viewing an AWS Batch compute environment that uses the SPOT_PRICE_CAPACITY_OPTIMIZED allocation strategy fails on tw CLI versions earlier than v0.8, which don't support it.

To resolve, upgrade to CLI v0.9 or later, where this was addressed.

Segmentation faults​

Legacy tw CLI versions can produce segmentation faults on older operating systems.

To resolve, upgrade the tw CLI to the latest version. If the fault persists, use the Java JAR-based build.

You are trying to connect to an insecure server…​

ERROR: You are trying to connect to an insecure server: http://hostname:port/api if you want to force the connection use '--insecure'. NOT RECOMMENDED!

This error occurs when your Seqera host accepts connections over insecure HTTP instead of HTTPS.

To resolve, configure the host to accept HTTPS connections. If it can't, add the --insecure flag before the CLI command:

tw --insecure info
caution

HTTP must not be used in production environments.

ExpiredToken errors during large uploads​

Failed to upload file: HTTP 400, Message: <Error><Code>ExpiredToken</Code><Message>The provided token has expired.</Message>...

This error occurs when a tw data-links upload transfer outlives the signed upload URLs that Platform issued when the upload started. tw CLI versions earlier than v0.40.0 cannot refresh those URLs. The remaining parts fail.

To resolve, upgrade to tw CLI v0.40.0 or later. For AWS S3 and Seqera Compute data links, the CLI requests fresh URLs for the remaining parts and continues the upload. See Large uploads.

Relaunch a run​

Relaunch a run with the tw runs relaunch command:

tw runs relaunch -i 3adMwRdD75ah6P -w 161372824019700

  Workflow 5fUvqUMB89zr2W submitted at [org / private] workspace.


tw runs list -w 161372824019700

  Pipeline runs at [org / private] workspace:

     ID             | Status    | Project Name   | Run Name        | Username    | Submit Date
    ----------------+-----------+----------------+-----------------+-------------+-------------------------------
     5fUvqUMB89zr2W | SUBMITTED | nf/hello       | magical_darwin  | seqera-user | Tue, 10 Sep 2022 14:40:52 GMT
     3adMwRdD75ah6P | SUCCEEDED | nf/hello       | high_hodgkin    | seqera-user | Tue, 10 Sep 2022 13:10:50 GMT

On this Page