This is a public tracker for internal ticket ES-178.

Problem

Validation error is thrown when you attempt to use the Platform CLI to execute an [pipeline launch](tower-cli/USAGE.md at master · seqeralabs/tower-cli ) (affects both saved and unsaved types)

How To Recreate

1. Create a CE with a resource label (e.g. 'bug=true').

2. Point the Platform CLI to the instance where your CE exists.

3. Try to invoke a pipeline (this is an example of unsaved pipeline):

   tw -o json -v launch --labels="bug=true" --workspace WORKSPACE_ID --compute-env CE_NAME --name test --revision master https://github.com/nextflow-io/hello
   

   NOTE: If using a Cloud instance, ensure your role is Maintain so that you are caught in validation logic requiring your launch RLs to match the CE RLs.

Expected Result

Run should start successfully.

Actual Result

1. Platform CLI sends resource-type label (key=value pattern) as a normal label.

   Oct 17, 2025 12:31:35 PM org.glassfish.jersey.logging.LoggingInterceptor log
   INFO: 4 * Sending client request on thread main
   4 > POST https://autodc.dev-seqera.net/api/labels?workspaceId=42928511310162
   4 > Accept: application/json
   4 > Authorization: [redacted]
   4 > Content-Type: application/json
   4 > User-Agent: tw/0.15.0 (java)
   {"name":"bug=true","resource":false,"isDefault":false}
   

2. Platform throws a validation error:

   ERROR: Label name must contain a minimum of 2 and a maximum of 39 alphanumeric characters separated by dashes or underscores

Fix Consideration

Seqera Engineering advises this problems impacts both:

1. Pipeline invocation
2. Studios invocation